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

(in the future) re-enable Time tests on apple m1 #6687

Closed
maniwani opened this issue Nov 18, 2022 · 0 comments
Closed

(in the future) re-enable Time tests on apple m1 #6687

maniwani opened this issue Nov 18, 2022 · 0 comments
Labels
A-Time Involves time keeping and reporting 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

Comments

@maniwani
Copy link
Contributor

I fixed the problem that caused #6377 with rust-lang/rust#103594, so when 1.67 drops we can re-enable those tests.

@maniwani maniwani added C-Bug An unexpected or incorrect behavior S-Needs-Triage This issue needs to be labelled C-Testing A change that impacts how we test Bevy or how users test their apps A-Time Involves time keeping and reporting O-MacOS Specific to the MacOS (Apple) desktop operating system and removed C-Bug An unexpected or incorrect behavior S-Needs-Triage This issue needs to be labelled labels Nov 18, 2022
@bors bors bot closed this as completed in bfafa78 Jan 28, 2023
ItsDoot pushed a commit to ItsDoot/bevy that referenced this issue Feb 1, 2023
# Objective

- Fixes bevyengine#6687

## Solution

- The future is now! Rust 1.67 was released with the fix
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Time Involves time keeping and reporting 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
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant