develooper Front page | perl.perl5.porters | Postings from December 2020

Re: committers: do you use dromedary?

Thread Previous | Thread Next
Tony Cook
December 24, 2020 22:29
Re: committers: do you use dromedary?
Message ID:
I used the old dromedary when I was working on 64-bit support for
Storable, since with 96GB of memory I could test some of the possible
>2**32 cases.

I never signed up for the more recent dromedary, since I have roughly
equivalent (or better, recently) hardware on hand.

I don't have access to a modern Mac though (I have a 2010 Mac Mini


On Thu, Dec 24, 2020 at 03:31:37PM -0500, Ricardo Signes wrote:
> Once upon a time, a sponsor provided a server called dromedary.  It was a big beefy hunky of hardware with a lot of RAM and a bunch of cores.  It compiled perl very fast.  Some people used it for bisecting, some for testing a bunch of different versions of perl, and so on.
> Later, a second dromedary existed and was used, but less.
> I've been trying to get a handle on the various resources we rely on, and dromedary has come up.  If there's to be a third iteration of this box:  *Who will use it and for what?*
> I guess I'd start off thinking it's like the old one:  used by committers as a powerful place to do a lot of compiling and testing.  But is that right?  If you are a committer and would (or would not!) use it, please say so, and let me know what you'd be using it for.  (What else we might use a bunch of compute for is another question.  This is more about a box where you'd have a shell.)
> -- 
> rjbs

Thread Previous | Thread Next Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About