Bug 99811

Summary: Incorrect test case path in TestExpectations of qt-5.0-wk2 platform
Product: WebKit Reporter: pdeng6 <pan.deng>
Component: WebCore Misc.Assignee: Nobody <webkit-unassigned>
Status: RESOLVED FIXED    
Severity: Normal CC: eric, simonjam, tonyg, webkit.review.bot
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Patch none

pdeng6
Reported 2012-10-18 23:13:26 PDT
item webkit.org/b/84893 http/tests/w3c/webperf/proposal/Intel/user-timing should be webkit.org/b/84893 http/tests/w3c/webperf/submission/Intel/user-timing
Attachments
Patch (1.56 KB, patch)
2012-10-18 23:21 PDT, pdeng6 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
pdeng6
Comment 1 2012-10-18 23:21:24 PDT
Created attachment 169557 [details] Patch
WebKit Review Bot
Comment 2 2012-10-19 08:27:38 PDT
Comment on attachment 169557 [details] Patch Rejecting attachment 169557 [details] from commit-queue. Failed to run "['/mnt/git/webkit-commit-queue/Tools/Scripts/webkit-patch', '--status-host=queues.webkit.org', '-..." exit_code: 1 ERROR: /mnt/git/webkit-commit-queue/Source/JavaScriptCore/ChangeLog neither lists a valid reviewer nor contains the string "Unreviewed" or "Rubber stamp" (case insensitive). Full output: http://queues.webkit.org/results/14473007
Tony Gentilcore
Comment 3 2012-10-19 08:43:38 PDT
Eric, any idea what happened to the commit queue here? It is complaining about a file that isn't in the patch (JavaScriptCore/ChangeLog).
Eric Seidel (no email)
Comment 4 2012-10-19 09:25:49 PDT
Comment on attachment 169557 [details] Patch It's just try again. It's possible the checkout on one of the cq machines got confused.
WebKit Review Bot
Comment 5 2012-10-19 09:54:06 PDT
Comment on attachment 169557 [details] Patch Clearing flags on attachment: 169557 Committed r131909: <http://trac.webkit.org/changeset/131909>
WebKit Review Bot
Comment 6 2012-10-19 09:54:09 PDT
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.