Closed
Bug 358371
Opened 19 years ago
Closed 19 years ago
nagios - resolve lack of updating for XULRunner trunk control file
Categories
(mozilla.org Graveyard :: Server Operations, task)
mozilla.org Graveyard
Server Operations
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: nthomas, Assigned: justdave)
Details
The test on XULRunner trunk nightly files has not picked up the CVS change that removed the 1.8b5 versions (2006-10-24 10:50 PDT).
The test:
https://nagios.mozilla.org/nagios/cgi-bin/extinfo.cgi?type=2&host=surf&service=Nightly+Builds+-+XULRunner+trunk
Current file contents:
http://lxr.mozilla.org/mozilla/source/tools/tinderbox-configs/monitoring/XULRunner_trunk.txt
Perhaps a CVS conflict ?
| Reporter | ||
Comment 1•19 years ago
|
||
Something is going wrong with the SeaMonkey trunk test too. The windows-xpi/ files were just added in rev 1.3 of Seamonkey_trunk.txt, and all 13 are currently stale (tinderbox problems), but only gre-win32-installer.zip and xpcom.xpi show up in the error. Some of the control file must have changed, since the extraneous linux-xpi/xpi tests are now removed and no longer feature in the reported error.
Also the windows installers & zip are stale but are not reported as such (bug 358527 is for the stale files problem)
| Assignee | ||
Comment 2•19 years ago
|
||
yeah, XULRunner_trunk file had a cvs conflict. No clue how, I must have done something to it when testing and forgot to put it back. Conflict nuked, it's current with CVS now, and things look normal now.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
| Assignee | ||
Comment 3•19 years ago
|
||
(In reply to comment #1)
> Something is going wrong with the SeaMonkey trunk test too.
And just for the record... the Seamonkey_trunk file had windows linefeeds in it, and that was screwing it up. I changed it to unix linefeeds and checked it in, and also fixed the test to be able to deal with it just in case it happens again in the future.
Updated•10 years ago
|
Product: mozilla.org → mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•