Skip to content
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

Jump to bottom

multiTouchPointsReleaseSecondPoint.html infrastructure test flaky-failing on Chrome #27200

Open
stephenmcgruer opened this issue Jan 15, 2021 · 3 comments
Open

multiTouchPointsReleaseSecondPoint.html infrastructure test flaky-failing on Chrome #27200

stephenmcgruer opened this issue Jan 15, 2021 · 3 comments
Assignees
@LanWei22
Labels
flaky infra priority:backlog

Comments

@stephenmcgruer
Copy link
Contributor

I'm not sure if something has changed here (in the test? in testdriver? in Chrome itself?), but recently my changes to tools/ keep triggering failures in multiTouchPointsReleaseSecondPoint.html (e.g. https://community-tc.services.mozilla.com/tasks/Clz4V0WiQ9aYFXaIOJsQiw/runs/0/logs/https%3A%2F%2Fcommunity-tc.services.mozilla.com%2Fapi%2Fqueue%2Fv1%2Ftask%2FClz4V0WiQ9aYFXaIOJsQiw%2Fruns%2F0%2Fartifacts%2Fpublic%252Flogs%252Flive.log):

/infrastructure/testdriver/actions/multiTouchPointsReleaseSecondPoint.html
  FAIL TestDriver actions: two touch points with one moving one pause - assert_array_equals: lengths differ, expected array ["pointerdown", "pointerdown", "pointermove", "pointerup", "pointerup"] length 5, got ["pointerdown", "pointerdown", "pointermove", "pointerup"] length 4
    at Test.<anonymous> (http://web-platform.test:8000/infrastructure/testdriver/actions/multiTouchPointsReleaseSecondPoint.html:52:7)
    at Test.step (http://web-platform.test:8000/resources/testharness.js:2044:25)
    at http://web-platform.test:8000/resources/testharness.js:2085:32

We'll need to add an infrastructure expectation for this.

cc @LanWei22
@stephenmcgruer
Copy link
Contributor Author

See #20838 for a previous case where this test was failing (over a year ago now)

@stephenmcgruer stephenmcgruer mentioned this issue Jan 15, 2021
Merged
stephenmcgruer added a commit that referenced this issue Jan 15, 2021
@stephenmcgruer
multiTouchPointsReleaseSecondPoint.html - Add FAIL expectation for Ch…
54a1bdd 
…rome on non-Mac

Closes #27200
@stephenmcgruer stephenmcgruer mentioned this issue Jan 15, 2021
Closed
@stephenmcgruer
Copy link
Contributor Author

It's possible something is flaky here; my attempt to add metadata failed because the test passed rather than failed! #27201

@stephenmcgruer stephenmcgruer mentioned this issue Jan 21, 2021
Merged
@stephenmcgruer stephenmcgruer changed the title multiTouchPointsReleaseSecondPoint.html infrastructure test failing on Chrome multiTouchPointsReleaseSecondPoint.html infrastructure test flaky-failing on Chrome Jan 21, 2021
@stephenmcgruer
Copy link
Contributor Author

This is being marked flaky in #27278 (review) so lowering the priority and assigning LanWei22 to investigate. This test no longer passes reliably on any browser!

@zcorpan zcorpan added the flaky label Feb 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@LanWei22 LanWei22

Labels
flaky infra priority:backlog
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

multiTouchPointsReleaseSecondPoint.html - Add FAIL expectation for Ch… web-platform-tests/wpt
3 participants
@stephenmcgruer @zcorpan @LanWei22