-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Add a Test-Sequence header to the webkitpy <-> WKTR/DRT server protocol #49978
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
EWS run on previous version of this PR (hash 8b56f40) |
The only notable failures this finds are on mac-wk1, --- /Volumes/Data/worker/macOS-Sonoma-Release-WK1-Tests-EWS/build/layout-test-results/scrollbars/scrollevent-iframe-no-scrolling-wheel-expected.txt
+++ /Volumes/Data/worker/macOS-Sonoma-Release-WK1-Tests-EWS/build/layout-test-results/scrollbars/scrollevent-iframe-no-scrolling-wheel-actual.txt
@@ -1,3 +1,3 @@
-mouseScrollByXandYContinuously: Unable to locate target view for current mouse location.Content-Type: text/plain
+mouseScrollByXandYContinuously: Unable to locate target view for current mouse location.Test-Sequence: 495
Not scrolled by WheelEvent: SUCCESS For
And on the re-run on worker 17:
This suggests |
https://bugs.webkit.org/show_bug.cgi?id=298004 Reviewed by NOBODY (OOPS!). This keeps count of the number of run test commands sent on both sides of the protocol, allowing some basic synchronization. It is less ideal than setting some abstract UUID (because incrementing accidentally is possible), but this is landable in a much lower-impact way that doesn't break the communication protocol, allowing older WKTR/DRT builds (e.g., from build archives) to still work with current webkitpy. We report failures as CRASH, because a driver synchronization issue is a significant one. Of course, by the point this occurs, it's reporting a _following_ test as CRASH (and almost certainly the _immediately_ following test), and not the one that caused the synchronization issue to start with. Explanation of why this fixes the bug (OOPS!).
8b56f40
to
b5b0a0d
Compare
EWS run on current version of this PR (hash b5b0a0d)
|
b5b0a0d
b5b0a0d