New wpt failures in /webdriver/tests/bidi/input/perform_actions/ [pointer_pen.py, pointer_touch.py]
Categories
(Remote Protocol :: WebDriver BiDi, defect, P5)
Tracking
(firefox135 fixed)
Tracking | Status | |
---|---|---|
firefox135 | --- | fixed |
People
(Reporter: wpt-sync, Assigned: whimboo)
References
Details
(Whiteboard: [webdriver:m14][wpt])
Attachments
(1 file)
Syncing wpt PR 49759 found new untriaged test failures in CI
Tests Affected
New Tests That Don't Pass
- /webdriver/tests/bidi/input/perform_actions/pointer_pen.py [wpt.fyi]
- test_pen_pointer_in_shadow_tree[outer-open]:
FAIL
(Chrome:PASS
, Safari:ERROR
) - test_pen_pointer_in_shadow_tree[outer-closed]:
FAIL
(Chrome:PASS
, Safari:ERROR
) - test_pen_pointer_in_shadow_tree[inner-open]:
FAIL
(Chrome:PASS
, Safari:ERROR
) - test_pen_pointer_in_shadow_tree[inner-closed]:
FAIL
(Chrome:PASS
, Safari:ERROR
) - test_pen_pointer_properties:
FAIL
(Chrome:PASS
, Safari:ERROR
)
- test_pen_pointer_in_shadow_tree[outer-open]:
- /webdriver/tests/bidi/input/perform_actions/pointer_touch.py [wpt.fyi]
- test_touch_pointer_properties_angle_twist:
FAIL
(Chrome:PASS
, Safari:ERROR
)
- test_touch_pointer_properties_angle_twist:
CI Results
Gecko CI (Treeherder)
GitHub PR Head
Notes
These updates will be on mozilla-central once bug 1938085 lands.
Note: this bug is for tracking fixing the issues and is not
owned by the wpt sync bot.
This bug is linked to the relevant tests by an annotation in
https://github.com/web-platform-tests/wpt-metadata. These annotations
can be edited using the wpt interop dashboard
https://jgraham.github.io/wptdash/
If this bug is split into multiple bugs, please also update the
annotations, otherwise we are unable to track which wpt issues are
already triaged. Resolving as duplicate or closing this issue should
be cause the bot to automatically update or remove the annotation.
Assignee | ||
Comment 1•2 months ago
|
||
All of these failing tests are already marked as FAIL
. So I assume that something is wrong with the bot in reporting old failures as new?
Comment 2•2 months ago
|
||
(In reply to Henrik Skupin [:whimboo][⌚️UTC+2] from comment #1)
All of these failing tests are already marked as
FAIL
. So I assume that something is wrong with the bot in reporting old failures as new?
The bot reports on all the failures which don't have the bug specified for them in metadata, it doesn't check the git/hg diff.
Assignee | ||
Comment 3•2 months ago
|
||
Updated•2 months ago
|
Assignee | ||
Updated•2 months ago
|
Comment 5•2 months ago
|
||
bugherder |
Description
•