tests/wlcs: Drop frame_timestamp_increases from expected failures #2976
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Mir has actually been sending correct (or, at least, not wildly incorrect) timestamps on frame events for quite some time, but the test itself was broken. Now that the test is not broken (and was then fixed *again*), remove it from the XFAIL list so CI will pass again.
|
Before canonical/wlcs#298 lands this will have some test failures ;) |
|
Now that the WLCS fix has landed, this should be landable. Retriggering the failed builds. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Mir has actually been sending correct (or, at least, not wildly incorrect) timestamps on frame events for quite some time, but the test itself was broken.
Now that the test is not broken (and was then fixed again), remove it from the XFAIL list so CI will pass again.