171471 - RFE: Provide new, faster SPARC+Sun Workshop tinderbox machine for SeaMonkey-Ports

Status: RESOLVED INCOMPLETE

(Webtools Graveyard :: Tinderbox, enhancement)

Description

[Roland Mainz]

RFE: Provide new, faster tinderbox machine for SeaMonkey-Ports

Currently there is only one machine on Seamonkey-Ports which runs with the Sun
Workshop compiler using a minimum set (to lower the tinderbox cycle time) of
tests&&extensions.

It would be nice if there would be a spare machine around at Sun which is faster
and has more memory to run the full set of tinderbox tests and maybe some
additional tests (like the automated purify-like tests described in bug 171449
("RFE: Run Solaris/Workshop tinderbox tests under dbx control for automated
Purify(-like) checks") and has a faster cycle time (to avoid that we have to
wait four, five or six hours until we see that a checkin "broke" something).

Comment 1

[Pete Zha]

Roland,
What is "speedracer" on ports boxes?
Is it what you need?

Comment 2

[Pete Zha]

And SunOS/sparc 5.7 nebiros Dep?

Comment 3

[Chris McAfee]

speedracer is using gcc, not the workshop compiler.  We would need a license for
workshop, that is a bit of work.

Comment 4

[Roland Mainz]

Pete Zha wrote:
> What is "speedracer" on ports boxes?
> Is it what you need?

No, "speedracer" is our Xlib port tinderbox.

> And SunOS/sparc 5.7 nebiros Dep?

... that's the main Solaris tinderbox machine running Sun Workshop.

----

I was thinking about a newer, faster machine which has a cycle time of less than
two or three hours (e.g. less than half the time "nebiros" currently needs) for
a full rebuild (using the Sun Workshop) compiler.
Since the tinderbox system uses only CVS (for getting the source) and email (for
sending the status) such a machine can be everywhere (for example the AIX
tinderbox sits in an IBM lab :) , even behind a firewall[1].
We only need someone from Sun who has a UltraSPARC-3 or US-3i-based box around
somewhere which can contribute some spare CPU cycles.

[1]=technically there is a slight risk that someone with Mozilla.org CVS account
may use this to upload an exploit ("worm" etc.) which is executed at build time,
but this issue can be solved by various countermeasures (no details here in the
public... :) - and since CVS write access to the mozilla.org CVS repository is
restricted and traceable (e.g. we are able track the bad guy and even get
his/her email, phone and FAX numbers, street, city etc. =:-) this kind of risk
should be very low... :)

Comment 5

[Kyle Yuan]

Now it's in our to-do list.

Comment 6

[Frank Wein [:mcsmurf]]

SeaMonkey-Ports now has two SunOS 5.10 boxen, one Sun-Blade-2500, running Sun Studio 10 and a x86 box, also running Sun Studio 10.

Comment 7

[Robert Kaiser]

This is not making sense any more, the facts come from a long-gone time.