Closed Bug 681814 Opened 14 years ago Closed 14 years ago

Mochitests should show the slavename in the scrape

Categories

(Tree Management Graveyard :: TBPL, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: philor, Assigned: philor)

References

Details

Attachments

(1 file)

Tinderbox-based tbpl shows the slave name in both the summary popup and at the top of the brief log (well, that part is Tinderbox), but with usebuildbot=1, you don't get the slave name in the summary, and you don't get it from getParsedLog.php except with &full=1. That makes it harder to notice that just one slave is the one that keeps doing foo, and more of a hassle to ping |buildduty about which slave did bar and needs a smacking.
Probably the best thing to do is to stop hiding it in the scrape (since it can be useful to know either "that green run was on the same slave" or "that one green run was because it was a different slave" even though we don't show a popup for green runs), but that's dependent on bug 582697 and its dependencies to clean up both our regexes and releng's TinderboxPrinting.
Depends on: 582697
this would also be great for me when looking at the output of tinderboxpuslog robot.
I had high hopes that someone smart would just fix this for me everywhere, but given that that's not going to happen, I split it into bite-size chunks, some of which I'll be able to do. bug 713574 for tbplbot bug comments bug 713575 for brief logs bug 713576 for Talos scrape
Assignee: nobody → philringnalda
Status: NEW → ASSIGNED
Keywords: regression
Summary: usebuildbot should parse and show the slave name → Mochitests should show the slavename in the scrape
Attached patch fix v.1Splinter Review
Arguably, the right fix here is to dismantle the whole elegant whateverthatis that picks which function to call, since talos is now done before it ever gets down there, Everythingelse I think died with 1.9.1, if not before, Unit Test probably wants the same generic scraper that doesn't drop slavename treatment, at which point everything is either generic or talos. However, since we throw away logs after four days right now and the newest Unit Test run is two weeks old, I'd have to trigger a full set of builds and tests on every platform on 1.9.2 just to be sure it doesn't have garbage in its scrape, and the function is such an elegant assemblage of braces and parens and bits and bobs that the last time I tried to dismantle it, I couldn't even get to where I could tell what the syntax error I caused meant. So, this gives me the slavename in the scrape for mochitests, which makes me happy.
Attachment #584357 - Flags: review?(mstange)
Attachment #584357 - Flags: review?(mstange) → review+
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Depends on: 715567
Product: Webtools → Tree Management
Product: Tree Management → Tree Management Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: