740754 - Most of SeaMonkey builds report "FAIL: graph server unreachable" (graphs-old.mozilla.org) since March 28th, 2012

Status: VERIFIED FIXED

(SeaMonkey :: Release Engineering, defect, P2)

Description

[Serge Gautherie (:sgautherie)]

-central, -beta, -aurora, ..., are affected:
'B' builds are purple, yet tests still run.

Comment 1

[Serge Gautherie (:sgautherie)]

NB: It would be interesting to know what the difference is with the few builds that are still green.

Comment 2

[Robert Kaiser]

AFAIK, that graph server has been turned off for good. I'd guess that the green ones just don't push anything to a graphs server.

Comment 3

[Serge Gautherie (:sgautherie)]

(In reply to Robert Kaiser (:[e-mail]) from comment #2)
> AFAIK, that graph server has been turned off for good. I'd guess that the
> green ones just don't push anything to a graphs server.

That was my guess too.

Would you know which bug turned graphs-old.m.o off?
If SeaMonkey is not ready for the new API yet, then this step should be disabled in the meantime.

We should also check why some of our boxes (cb-seamonkey-win32-0x 'build', at least) don't behave like the other ones...

Comment 4

[Robert Kaiser]

(In reply to Serge Gautherie (:sgautherie) from comment #3)
> Would you know which bug turned graphs-old.m.o off?

No, but it has been planned for ages and warning had been sent out.

> If SeaMonkey is not ready for the new API yet, then this step should be
> disabled in the meantime.

Probably, as I doubt anyone in SeaMonkey looks at this data at all, just like with crash data. I guess either doesn't care or is undermanned (the latter would mean that some time should be spent actively recruiting people into the community).

Comment 5

[Justin Wood (:Callek)]

(In reply to Robert Kaiser (:[e-mail]) from comment #4)
> (In reply to Serge Gautherie (:sgautherie) from comment #3)
> > Would you know which bug turned graphs-old.m.o off?
> 
> No, but it has been planned for ages and warning had been sent out.

I knew it was planned -- But I either didn't get the warning, missed the warning, or forgot about the warning; as it relates to WHEN it was to be turned off.

I distinctly remember someone saying something about a new API needed that we'd need to adapt on our end, but I can't find any indication of that atm.

So I pushed what I THINK is the fix
http://hg.mozilla.org/build/buildbot-configs/rev/0e7e9b78b969
And reconfigured the buildbot master

Leaving open until its proven to have fixed it, if it doesn't please comment once you know, and if it does, please comment+resolve. I'll hope to look over the weekend again to be sure.

Comment 6

[Serge Gautherie (:sgautherie)]

(In reply to Serge Gautherie (:sgautherie) from comment #3)
> We should also check why some of our boxes (cb-seamonkey-win32-0x 'build',
> at least) don't behave like the other ones...

After a closer look, it seems to be all "WINNT 5.2 comm-central-trunk build" builds (and maybe branches too?).

Actually, that's expected: as FF, SM Windows Opt builds don't run "(Z) Codesighs".


(In reply to Justin Wood (:Callek) from comment #5)

> I distinctly remember someone saying something about a new API needed that
> we'd need to adapt on our end, but I can't find any indication of that atm.

New API was mentioned in SM bug 71220 but without details...

> http://hg.mozilla.org/build/buildbot-configs/rev/0e7e9b78b969

Ftr, you simply s/graphs-old.mozilla.org/graphs.mozilla.org/.

> Leaving open until its proven to have fixed it, if it doesn't please comment
> once you know, and if it does, please comment+resolve. I'll hope to look
> over the weekend again to be sure.

http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1333177994.1333186192.24903.gz&fulltext=1
Linux comm-central-trunk build on 2012/03/31 00:13:14
{
graph server post results complete
}

Better :-)
Let's wait for all 'B' builds to get back to green...

Comment 7

[Justin Wood (:Callek)]

Looks like that solved this bug

Comment 8

[Serge Gautherie (:sgautherie)]

V.Fixed