Closed Bug 1147835 Opened 5 years ago Closed 5 years ago

SeaMonkey linux* builders are not connected to master due to failing runslave.py's guess_basedir()

Categories

(SeaMonkey :: Release Engineering, defect)

x86
Windows 7
defect
Not set

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: ewong, Assigned: ewong)

References

Details

Attachments

(1 file, 1 obsolete file)

With the recent change in runslave.py (http://hg.mozilla.org/build/puppet/rev/0d48d0ca9f54), SeaMonkey's linux* slaves are failing the guess_basedir()
check.

I haven't discovered why it's even getting to that stage yet (still reading
up on runslave.py), but one option is to add seamonkey's linux64 pattern
to the list of slave_match() check.
this is one option.
Assignee: relops → ewong
Status: NEW → ASSIGNED
Attachment #8583788 - Flags: review?(bugspam.Callek)
Perhaps it's time for SM to stop following the moco puppet repository?
(In reply to Dustin J. Mitchell [:dustin] from comment #2)
> Perhaps it's time for SM to stop following the moco puppet repository?

Probably.  However we'd still need to patch this bustage somehow....
Comment on attachment 8583788 [details] [diff] [review]
add SeaMonkey's slaves to check (v1)

Review of attachment 8583788 [details] [diff] [review]:
-----------------------------------------------------------------

I'm going to defer this seamonkey approach to coop, who can tell me if he's ok with us patching this file, or doing anything here.

I have a gut feeling that if we do patch here, we'd want to do sea-* as part of the match, but I'm unsure at present.
Attachment #8583788 - Flags: feedback?(coop)
Comment on attachment 8583788 [details] [diff] [review]
add SeaMonkey's slaves to check (v1)

Review of attachment 8583788 [details] [diff] [review]:
-----------------------------------------------------------------

(In reply to Justin Wood (:Callek) from comment #4) 
> I'm going to defer this seamonkey approach to coop, who can tell me if he's
> ok with us patching this file, or doing anything here.
> 
> I have a gut feeling that if we do patch here, we'd want to do sea-* as part
> of the match, but I'm unsure at present.

I agree with Dustin: SeaMonkey should be maintaining a fork of this code and updating it on their own schedule to avoid exactly these types of issues.
Attachment #8583788 - Flags: feedback?(coop) → feedback-
Depends on: 1148229
Component: RelOps: Puppet → Release Engineering
Product: Infrastructure & Operations → SeaMonkey
QA Contact: dustin
Version: other → unspecified
Since this no longer touches relops' puppet, moving to SeaMonkey::RelEng.
Attachment #8590633 - Flags: review?(bugspam.Callek)
Attachment #8590633 - Flags: review?(bugspam.Callek) → review+
Comment on attachment 8590633 [details] [diff] [review]
change repo url in seamonkey-config.pp (v1)

Pushed to SeaMonkey/puppet:
http://hg.mozilla.org/SeaMonkey/puppet/rev/8059d077b351
Pushed to SeaMonkey/puppet the backout of cset 0d48d0ca9f54:
http://hg.mozilla.org/SeaMonkey/puppet/rev/7e6b67b6a53d

+ modified the .hg/hgrc in seapuppet's /etc/puppet/production to
reflect the new repo http://hg.mozilla.org/SeaMonkey/puppet.

Now,  the linux slaves are starting to connect with the master again.
Comment on attachment 8583788 [details] [diff] [review]
add SeaMonkey's slaves to check (v1)

No longer need this patch.
Attachment #8583788 - Attachment is obsolete: true
Attachment #8583788 - Flags: review?(bugspam.Callek)
The linux* slaves are back (minus -5 and -7 due to them being AWOLish).

Closing this bug.
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.