Bug 61464 - TestFailures page shows failures from a not-most-recent build when one slave is taking a long time to finish a build
Summary: TestFailures page shows failures from a not-most-recent build when one slave ...
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Adam Roben (:aroben)
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2011-05-25 13:20 PDT by Adam Roben (:aroben)
Modified: 2011-05-27 10:15 PDT (History)
2 users (show)

See Also:

Attachments
Don't assume that builds finish in the order they were started (2.38 KB, patch)
2011-05-25 13:26 PDT, Adam Roben (:aroben) 		koivisto: review+
Details | Formatted Diff | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Adam Roben (:aroben) 2011-05-25 13:20:46 PDT 
If one slave is taking a long time to finish a build and other newer builds have finished since the slow slave began its build, the TestFailures page will show failures from the build before the not-yet-finished build, rather than showing failures from the most-recently-finished build.
Comment 1 Adam Roben (:aroben) 2011-05-25 13:26:28 PDT 
Created attachment 94848 [details]
Don't assume that builds finish in the order they were started
Comment 2 Adam Roben (:aroben) 2011-05-26 06:20:47 PDT 
Committed r87380: <http://trac.webkit.org/changeset/87380>
Comment 3 Michael Saboff 2011-05-27 10:15:29 PDT 
<rdar://problem/9515584>