Closed Bug 607245 Opened 14 years ago Closed 14 years ago

MoMe TBPL: SeaMonkey 2.0 'test mochitests' not showing up

Categories

(Mozilla Messaging Graveyard :: Server Operations, defect)

Product:
Mozilla Messaging Graveyard
Component:
Server Operations
Type:
defect
Priority:
Not set
Severity:
major

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: sgautherie, Assigned: gozer)

Details

{
Date: Sun, 29 Aug 2010 13:12:49 +0200
From: Serge Gautherie <sgautherie.bz@free.fr>
To: "Philippe M. Chiasson" <gozer@mozillamessaging.com>
CC: Robert Kaiser <kairo@kairo.at>

Hello,

I just noticed that these builds only "show up" when they are starred 
(from tinderbox waterfall):
if I hadn't looked at the latter, I wouldn't have noticed the 
perma-orange :-/

Can this be fixed somehow ?
Thanks.
}

bug still there.
Justin's been doing all the work on porting tbpl recently.

Please file a bug first in future and don't email gozer directly - we have other members of the team who can pick this sort of thing up if necessary.
Assignee: nobody → bugspam.Callek
http://tbpl.mozilla.org/?tree=Firefox3.5 doesn't try to group Mxx.

I guess we too should just disable this (near superfluous) feature for c-1.9.1 apps.
(In reply to comment #1)

> Justin's been doing all the work on porting tbpl recently.

Yeah, he just told me that at SeaMonkey/Developer Meeting:2010 ;-)

> Please file a bug first in future and don't email gozer directly - we have
> other members of the team who can pick this sort of thing up if necessary.

As I'm actually doing now. That was just the way I was used to, and it mostly worked fine.
(In reply to comment #2)
> I guess we too should just disable this (near superfluous) feature for c-1.9.1
> apps.

http://build.mozillamessaging.com/tinderboxpushlog/js/Config.js
{
  treesWithGroups: [
    "SeaMonkey",
    "SeaMonkey2.0",
    "Firefox",
    "TraceMonkey",
    "Jaegermonkey",
    "Electrolysis",
    "AddonsMgr",
    "MozillaTry",
    "Birch",
    "Cedar",
    "Maple",
  ],
}
Remove 'SeaMonkey2.0', and probably all the following ones too which seem to be m-c "apps".
Status: NEW → ASSIGNED
Done
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Not sure what was done,
but comment 4 is unchanged and TBPL (back to Oct 29/27/25th) still has this bug.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Serge:

http://hg.mozilla.org/users/gozer_mozillamessaging.com/tinderboxpushlog/rev/9e7296d68a1e

I assume of course, that he pushed that live (but I'm not sure on the latter). Either way this is done in code, I do agree with leaving it OPEN to see if that does FIX it though.
Landed the changes, but omitted to push them to production.
Status: REOPENED → RESOLVED
Closed: 14 years ago → 14 years ago
Resolution: --- → FIXED
(In reply to comment #8)
> Landed the changes, but omitted to push them to production.

By this comment, did you now push to production; planning to soon, or what? (just so we are clear)...

I have no [strong] opinion on the various courses of action possible though.
V.Fixed, per MoMe TBPL.
Status: RESOLVED → VERIFIED
Assignee: bugspam.Callek → gozer
You need to log in before you can comment on or make changes to this bug.