Closed Bug 231998 Opened 21 years ago Closed 13 years ago

Where did the 'Linux brad Clobber'/'Blamed Build Warnings' page disappear to?

Categories

(Webtools Graveyard :: Tinderbox, defect)

Product:
Webtools Graveyard
Component:
Tinderbox
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: sgautherie, Assigned: braddr)

References

(
URL
)

Details

It was still there on
{
 Blamed Build Warnings
 Linux brad Clobber (info) on 01/22 12:58
}
But I can't find it anywhere anymore :-(
Summary: Where did the 'Linux brad Clobber'/'Blamed Build Warnings' disappeared to ? → Where did the 'Linux brad Clobber'/'Blamed Build Warnings' page disappeared to ?
hardware problems.. diagnosing what part is acting up.  If it's anything more
serious than memory, it might stay down.
Status: NEW → ASSIGNED
not looking good.. can't tell if it's the cpu, memory, or motherboard.  memtests
are spontaneously rebooting after some number of passes.  I'm out of spare
hardware to do a good job of parts swapping to figure out exactly what's going on.

I know for sure the drives are ok, but that's about it.

Anyone have a spare machine with 2 scsi channels and decent processors they want
to donate to the cause?
> spontaneously rebooting

Hardware: Power failure ?

> out of spare hardware

Software: Would it be possible to shutdown another tinderbox instead, as 'brad'
is the (only) one with '(info)' !?
> Hardware: Power failure ?

Trust me, it's hardware related

> Software: Would it be possible to shutdown another tinderbox instead, as 'brad'
is the (only) one with '(info)' !?

I'm not sure what 'info' yuu're missing, that's just a reference to a web page
that talks about what the machine is and the os and compiler details.  Nothing
that affects the build.

Anyway, it's decided to stay up for a few hours so I went ahead and re-enabled
the build but with just one of the 2 cpu's.  I have no confidence that it'll
stay up for very long.  Also with half the normal cpu power the builds take one
hell of a long time.


I trust you !

My mistake about '(info)':
I meant the "'Blamed Build Warnings' page".

The '01/24 13:03' still misses it by the way...
Builds used to last for 1h10, this one took 1h51: +60%, not so bad :-|
The 'Blamed Build Warnings' page is back :-)

The buils take +/- 1h45, except the last one (2h10) :-|

Thanks.
(In reply to comment #4)

> Anyway, it's decided to stay up for a few hours so I went ahead and re-enabled
> the build but with just one of the 2 cpu's.  I have no confidence that it'll
> stay up for very long.

It seems to have been working nicely for two weeks;
Shall you try and re-enable the second cpu ?
'brad' computer disappeared again:
Last green build: 06/24 04:43 - 06/24 06:36 (= 1h53)
Last yellow build: 06/24 06:37 - [06/24 17:28 (= 10h51)]
Box is unstable as hell.  Consider it gone until/unless I can get it replaced.
Brendan:
Any hope to have it repaired (soon) ?
If not, could another existing box be reconfigured to generate the 'Blamed Build
Warnings' page (and any other alike informational settings) ?
Severity: major → critical
Serge: It's not my box, it's braddr's, so don't ask me about hope for repair.

If we have another box for doing these tests, leaf and chofmann will know.

/be
(resolved bug 84508 as a dup and moved it's cc'ed people to this one)

I redirected the build to MozillaTest to see if it'll stay running.  It has for a while, though a test is timing 
out.  I believe that failure to be external to my network.  That said, I still believe the box to be too 
unstable to be of value to mozilla.org any more and am reluctant to move it back to the SeaMonkey 
build tree.  An unstable build is worse than no build, imho.  I've priced replacement hardware and 
it's more than I care to invest at the moment.  Sigh.  Sorry.
more hardware coming soon in a few weeks...  ping me again in the middle of july
The box has stayed stable and successfully building mozilla for a few days now 
(a whole week?).  However, an ftp test seens to be timing out.  I tried nuking 
both the source and objdir's and starting the source tree over just in case it 
had gotten corrupted during the frequent crashes.  Still failing.  I'll see if 
I can figure out what's going on this weekend.

Chris, I don't mind continuing to donate the rack space, power, ac, etc, for a 
volunteer maintained system at all.  However, I lack the spare equipment to 
move the build elsewhere or the funding to buy a new system for just mozilla 
right now.  A new box in a mozilla.org hosted data center would certainly solve 
the problem though.

Later,
Brad
Is there a reason why TBox does not include a "build warnings" page based on the
the "comet" build? The "comet" build is a clobber build and does seem to include
all the warnings, so it seems to be just a question of making sure TBox produces
an appropriate warnings page out of it.
This weekend I played with the ftp test and it's only timing out from mozilla.  I have no trouble getting 
to it through command line ftp or wget.  I haven't tried to dig in and debug the actual problem.  I notice 
that bismark on the -ports tree is showing the same symptoms.  I upped the timeout value to a much 
larger number (1500 seconds) just to see if it was being slow for some reason.  No dice.  I can move 
this back to the main seamonkey page leaving it orange if that'd be of any value.
(In reply to comment #16)
> I can move 
> this back to the main seamonkey page leaving it orange if that'd be of any value.

I'd like this, at least to get back the Build Warnings page. (I hope)
(In reply to comment #16)
> This weekend I played with the ftp test and it's only timing out from mozilla.

Is this specific to the mozilla site ?
Or could you be seeing bug 251213 ?
http://bugzilla.mozilla.org/show_bug.cgi?id=251213

This bug was reponsible for the orangeness of the build, not any sort of local issue.  So, I've moved the 
box off of MozillaTest back to SeaMonkey.

Resolving this ticket.
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
(In reply to comment #19)
> Resolving this ticket.

The computer did 3 builds of 1h45 each. (then 1 of 2h40)
It used to take 1h10 with the two cpus enabled...


(In reply to comment #13)
> more hardware coming soon in a few weeks...  ping me again in the middle of july

Now we are:
Brad, Chris, can you see if a hardware "repair/enhancement" is (still) wanted,
or if you prefer to keep this computer the way it is currently (= "half-enabled") ?
This box seems to have disappeared again :-(

It was still there some days ago...
URL: http://tinderbox.mozilla.org/showbuil...
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Summary: Where did the 'Linux brad Clobber'/'Blamed Build Warnings' page disappeared to ? → Where did the 'Linux brad Clobber'/'Blamed Build Warnings' page disappear to?
Component: Tinderbox Platforms → Tinderbox
Product: mozilla.org → Webtools
Ancient, machine is long trashed.
Status: REOPENED → RESOLVED
Closed: 20 years ago → 13 years ago
Resolution: --- → INVALID
Blocks: 187015
Product: Webtools → Webtools Graveyard
You need to log in before you can comment on or make changes to this bug.