-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
[Merged by Bors] - ignore nanosec precision tests on apple m1 #6377
Closed
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
might be worth adding a comment that if rust-lang/rust#94100 gets merged that we can reenable the tests. |
hymm
approved these changes
Oct 26, 2022
I linked to rust-lang/rust#91417 |
alice-i-cecile
approved these changes
Oct 26, 2022
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
bors r+
alice-i-cecile
added
A-Build-System
Related to build systems or continuous integration
O-MacOS
Specific to the MacOS (Apple) desktop operating system
C-Testing
A change that impacts how we test Bevy or how users test their apps
labels
Oct 26, 2022
bors bot
pushed a commit
that referenced
this pull request
Oct 26, 2022
# Objective - Some tests are very flaky on a m1 - m1 currently have a 41 ns precision ## Solution - Do not run tests that compare a `Duration` or a `f64` on a m1 (and m2)
Pull request successfully merged into main. Build succeeded:
|
bors
bot
changed the title
ignore nanosec precision tests on apple m1
[Merged by Bors] - ignore nanosec precision tests on apple m1
Oct 26, 2022
james7132
pushed a commit
to james7132/bevy
that referenced
this pull request
Oct 28, 2022
# Objective - Some tests are very flaky on a m1 - m1 currently have a 41 ns precision ## Solution - Do not run tests that compare a `Duration` or a `f64` on a m1 (and m2)
ItsDoot
pushed a commit
to ItsDoot/bevy
that referenced
this pull request
Feb 1, 2023
# Objective - Some tests are very flaky on a m1 - m1 currently have a 41 ns precision ## Solution - Do not run tests that compare a `Duration` or a `f64` on a m1 (and m2)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-Build-System
Related to build systems or continuous integration
C-Testing
A change that impacts how we test Bevy or how users test their apps
O-MacOS
Specific to the MacOS (Apple) desktop operating system
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.
Objective
Solution
Duration
or af64
on a m1 (and m2)