talos try unable to pull builds



Release Engineering
10 years ago
5 years ago


(Reporter: bhearsum, Unassigned)


Firefox Tracking Flags

(Not tracked)



(1 attachment)



10 years ago
The Try Server Talos master can no longer pull builds -- it doesn't appear to be able to scrape the filenames correctly. I bet that the upgrade of Apache 2.0 -> Apache 2.2 earlier this week killed it. I won't have time to investigate further until next week.
Created attachment 320092 [details] [diff] [review]
possible fix

This is currently running on the tryperfmaster and seems to be working.  It does break some of the code that pulls dates out of file names, but that doesn't appear to be called anywhere.

There is a bug where if a build fails we end up picking up and testing the previous workable build.  We need some smarts in there to ignore changes that result in broken/non-existent builds.  But, I believe that this problem has been here for a while so it could be split off into another bug.
Attachment #320092 - Flags: review?(bhearsum)

Comment 2

10 years ago
Comment on attachment 320092 [details] [diff] [review]
possible fix

This looks great. You shouldn't need to worry about it pulling the latest build all the time because it won't build unless TinderboxPoller triggers it. There is a race condition here though, I think. If two builds end really close together you could end up pulling the second one twice and skipping the first one altogether. Both would be labeled as that build, however, so it's less serious than it could be. (That's how I'm reading this code at least, can you confirm that Rob?) If such a condition does exist it's not new though so I'm not worried about it here. We should fix it at some point, of course.
Attachment #320092 - Flags: review?(bhearsum) → review+
Checking in perfrunner.py;
/cvsroot/mozilla/tools/buildbot-configs/testing/talos/tryperfmaster/perfrunner.py,v  <--  perfrunner.py
new revision: 1.3; previous revision: 1.2
Last Resolved: 10 years ago
Resolution: --- → FIXED


5 years ago
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.