Bug 96118

Summary: Actually trigger the Android Tester
Product: WebKit Reporter: Peter Beverloo <peter>
Component: New BugsAssignee: Peter Beverloo <peter>
Status: RESOLVED FIXED    
Severity: Normal CC: abarth, wsiegrist
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Patch none

Peter Beverloo
Reported 2012-09-07 09:40:18 PDT
Actually trigger the Android Tester
Attachments
Patch (1.61 KB, patch)
2012-09-07 09:41 PDT, Peter Beverloo 		no flags
DetailsFormatted DiffDiff
Show Obsolete (1) View All Add attachment proposed patch, testcase, etc.
Peter Beverloo
Comment 1 2012-09-07 09:41:04 PDT
Created attachment 162790 [details] Patch
Peter Beverloo
Comment 2 2012-09-07 09:47:22 PDT
The builder does not actually activate the chromium-android-release-tests trigger, which means that (a) the build will never be uploaded, and (b) the tester won't get a signal to start. It can be triggered manually, but no builds being available makes that do a void operation. I'm an idiot. Sorry for the trouble.. We can restart sometime next week if it already caused enough hassle on the tree today.
Peter Beverloo
Comment 3 2012-09-07 11:17:13 PDT
Committed r127895: <http://trac.webkit.org/changeset/127895>
Peter Beverloo
Comment 4 2012-09-07 11:19:42 PDT
Comment on attachment 162790 [details] Patch Thank you, Adam :-). After a next restart we should be fine. As said, it'll be red for at least a week (or two), but it'll be there :-).
Note You need to log in before you can comment on or make changes to this bug.