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
Stop skipping css-logical tests in layout-2020 #29814
Conversation
@bors-servo try=wpt-2020 |
Stop skipping css-logical tests in layout-2020 <!-- Please describe your changes on the following line: --> --- <!-- Thank you for contributing to Servo! Please replace each `[ ]` by `[X]` when the step is complete, and replace `___` with appropriate data: --> - [X] `./mach build -d` does not report any errors - [X] `./mach test-tidy` does not report any errors - [ ] These changes fix #___ (GitHub issue number if applicable) <!-- Either: --> - [ ] There are tests for these changes OR - [X] These changes do not require tests because there is no change in behavior <!-- Also, please make sure that "Allow edits from maintainers" checkbox is checked, so that we can help you if you get stuck somewhere along the way.--> <!-- Pull requests that do not address these steps are welcome, but they will require additional verification as part of the review process. -->
I expected less failures TBH, since this should mostly be a style thing. |
It could be that some of these properties are disabled since Layout 2020 doesn't support writing modes. |
Ah, that explains it. Most of the logical longhands seem enabled, but if writing modes aren't supported, they will not be mapped as the tests expect. |
Test results for linux-wpt-layout-2020 from try job (#5122849423): Flaky unexpected result (1)
|
☀️ Test successful - checks-github |
@bors-servo r=mrobinson |
📌 Commit c1a9ff0 has been approved by |
Stop skipping css-logical tests in layout-2020 <!-- Please describe your changes on the following line: --> --- <!-- Thank you for contributing to Servo! Please replace each `[ ]` by `[X]` when the step is complete, and replace `___` with appropriate data: --> - [X] `./mach build -d` does not report any errors - [X] `./mach test-tidy` does not report any errors - [ ] These changes fix #___ (GitHub issue number if applicable) <!-- Either: --> - [ ] There are tests for these changes OR - [X] These changes do not require tests because there is no change in behavior <!-- Also, please make sure that "Allow edits from maintainers" checkbox is checked, so that we can help you if you get stuck somewhere along the way.--> <!-- Pull requests that do not address these steps are welcome, but they will require additional verification as part of the review process. -->
Test results for linux-wpt-layout-2020 from try job (#5123356858): Flaky unexpected result (1)
|
Test results for linux-wpt-layout-2013 from try job (#5123356858): Flaky unexpected result (14)
Stable unexpected results that are known to be intermittent (18)
Stable unexpected results (1)
|
💔 Test failed - checks-github |
@bors-servo retry |
Test results for linux-wpt-layout-2013 from try job (#5124719386): Flaky unexpected result (12)
Stable unexpected results that are known to be intermittent (22)
|
☀️ Test successful - checks-github |
./mach build -d
does not report any errors./mach test-tidy
does not report any errors