Closed Bug 235611 Opened 22 years ago Closed 21 years ago

BeOS "Bewildered" Tindebox not listed in Seamonkey ports

Categories

(Webtools Graveyard :: Tinderbox, defect)

Product:
Webtools Graveyard
Component:
Tinderbox
Platform:
x86
BeOS
Type:
defect
Priority:
Not set
Severity:
trivial

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: edward.dore, Assigned: dbaron)

Details

User-Agent: Build Identifier: Mozilla/5.0 (BeOS; U; BeOS BePC; en-US; rv:1.5b) Gecko/20030904 The tinderbox for the BeOS port of mozilla isn't showing up in the Seamonkey-ports tinderbox pages Reproducible: Always Steps to Reproduce: 1. 2. 3.
Assignee: mcafee → dbaron
Component: Tinderbox → Tinderbox Platforms
Product: Webtools → mozilla.org
QA Contact: timeless → mcafee
Version: Trunk → other
I don't own this machine, it is probably seawood's.?
Hmm, the cvs checkout timeout code seems to kill the whole script on BeOS. I bumped the timeout on bewildered since it's really slow -- but maybe I'll try to investigate this more later...
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
David, I'm the new maintainer on Bezilla.org now Pauls left and I was wondering what the specs of Bewildered are and where it is located as I want to try and update or even replace it with a more reliable and faster box. Thanks, Edward Dore
It's in the Mozilla Foundation office, and it's a Pentium II or III of some sort.
David, I would appreciate some advice on teh best way to go about replacing the box if I can raise the money.
Bewildered has disappeared again! David I'm trying to get my hands ona new and more reliable box, would I have to send this to the mozilla foundation or could it be set up off site? Edward
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
Anyone can setup a tinderbox and it doesn't have to reside at MF. Just follow the instructions at http://lxr.mozilla.org/mozilla/source/tools/tinderbox/INSTALL . Btw, I doubt it's a hardware problem though faster hardware never hurts. I used to be the admin for bewildered and the tinderbox scripts are extremely fragile under BeOS. As David mentioned, using the kill command to kill a process launched by the script causes the entire script to die.
Severity: blocker → trivial
The scripts crashed again, either that or the box has! We've moved a step closer to a new Tinderbox today with a well publicised request for hardware on several major BeOS sites. David, I'll let you know more when I do, and when I get this Tinderbox running I'm going to have to see what I can do about the reliability of the scripts, can you give me a more precise idea of the problem?
Do we have to have a seperate tinderbox for Firefox? The build seems to break quite often under BeOS and noone notices. Currently browser/components/migration is broken for instance, and it wasn't long ago some makefile wanted winhooks to be included. It would be nice to have that, as it seems I'm the one that has to track them down and fix them most of the time.
Currently no, there are only Windows, Linux and Mac firefox and Thunderbird Tinderbox's I am looking into putting upto two in for each for BeZilla if we get a suffiecient number of machines donated as it would be nice to have sepearte netserver and BONE build machines. We have allready had one machine pledged and I'm going to speak to someone else about the possibility of several more so things are looking up.David, do you know if it would be possible for these new machines etc. to be donated through the Mozila foundation so that the donators can get a tax break?
Firefox will be suffering from this. If we want to have quality in both Mozilla and Firefox, we need to have build bustage detected early. I spend most of the time fixing build bustage instead of investigating 'Download managers' bad beahviour, and it's wearing me out. Personally I think it's a waste of resources to use two boxes for Mozilla. Both will almost always be busted at same time, only advantage is one netserver and one bone-build. The negative is that one of them is of almost no use to the developers. Just the fact that Firefox under BeOS has been broken for weeks says that we are in BIG need of a TinderBox for Firefox. So I disagree STRONGLY with your opinion.
Fredrik, I am slightly confused, with what do you disagree? Maybe I should make myself a bit clearer, I intend to have, depending on the amount of hardware donated, 6 different tinderbox's, a netserver and a BONE tinderbox for firefox, a netserver and a BONE tinderbox for thunderbird and a netserver and a BONE tinderbox for saemonkey.
I understood your message as you where focusing on setting up several ordinary Mozilla builds first (netserver, bone, zeta?) and only after that a firefox tinderbox. I do hope that there will be a firefox tinderbox after first mozilla tinderbox as Firefox gets a lot of build bustage.
It's crashed again. You'll be glad to know that several machines have been pledged as Tinderbox's and we are currently aranging to have them shipped to me. Hopefuly we will have our own offsite Tinderbox setup mid-late April, possibly sooner. I do have a question, when people donate to Mozilla.org I understand taht they get a Tax break, would it be possbile to arange that teh Tinderbox's are donated through mozilla so that the donators get the same reward? By the way Fredrik, thanks for clarifying that, I understand what you are saying. Basically then plan is first the two Mozilla TinderBox's, then the two FireFx Tinderbox's then the two Thunderbird Tindoerbox's then anything else such as different configs, maybe SVG enabled although I would like to see this on all builds, I havn't quite figured the SVG system out yet, if anyone can help me please email me via edward dot dore at bezilla dot org Thanks, Edward Dore, BeZilla.org
The problems are at least partly related to the power failure at the foundation office on Saturday morning.
Power Failure? What happened? Are the box's not UPS protected etc?
The power went out. The machines at the office don't have a UPS.
(In reply to comment #14) > By the way Fredrik, thanks for clarifying that, I understand what you are > saying. Basically then plan is first the two Mozilla TinderBox's, then the two > FireFx Tinderbox's then the two Thunderbird Tindoerbox's then anything else > such as different configs, maybe SVG enabled although I would like to see this > on all builds, I havn't quite figured the SVG system out yet, if anyone can > help me please email me via edward dot dore at bezilla dot org Well then I hope there will be enough machines for at least one Firefox.
QA Contact: mcafee → dbaron
There should be enough, I just don't know when they will be here. Several PIII 550's have been donated in addition to the PIII 500 that will replace the current Tinderbox, I just don't know when they will be decommisioned and sent to us. The comapny still has to remove any sensitive info and aprove the hardware for donation etc. Edward
Status: UNCONFIRMED → NEW
Ever confirmed: true
Since BeWildered is appearing once again, I suggest this bug be resummarized, to somthing like BeOS Mozilla tinderbox problems, or somthing
I have resolved the bug (I thought David had done this) but I will keep the title as whenever the tinderbox disapears again it is better to repoen the bug than create a new one.
Status: NEW → RESOLVED
Closed: 22 years ago → 22 years ago
Resolution: --- → FIXED
sounds reasonable to me.
The box has disappeared again, along with the BSD/OS, 2xHP-UX, and the IRIX box's! Hopefully we won't have this problem for much longer when we get the new box's. By the way David, who owns the ucrrent Tinderbox as it was suggested taht we could auction it off to raise moeny for a new one as it is part of the BeOS history (and is guarenteed to run BeOS!)
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Status: REOPENED → RESOLVED
Closed: 22 years ago → 21 years ago
Resolution: --- → FIXED
Component: Tinderbox Platforms → Tinderbox
Product: mozilla.org → Webtools
Product: Webtools → Webtools Graveyard
You need to log in before you can comment on or make changes to this bug.