Bug 96118 - Actually trigger the Android Tester
Summary: Actually trigger the Android Tester
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Peter Beverloo
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-09-07 09:40 PDT by Peter Beverloo
Modified: 2012-09-07 11:19 PDT (History)
2 users (show)

See Also:

Attachments
Patch (1.61 KB, patch)
2012-09-07 09:41 PDT, Peter Beverloo 		no flags Details | Formatted Diff | Diff
Show Obsolete (1) 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 Peter Beverloo 2012-09-07 09:40:18 PDT 
Actually trigger the Android Tester
Comment 1 Peter Beverloo 2012-09-07 09:41:04 PDT 
Created attachment 162790 [details]
Patch
Comment 2 Peter Beverloo 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.
Comment 3 Peter Beverloo 2012-09-07 11:17:13 PDT 
Committed r127895: <http://trac.webkit.org/changeset/127895>
Comment 4 Peter Beverloo 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 :-).