-
-
Notifications
You must be signed in to change notification settings - Fork 3.9k
Doctests for bevy_gizmos run for too long #11034
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
Comments
I was able to reproduce the issue! For some reason its only laggy on doctests. Unit tests work perfectly fine. /// ```
/// use bevy::gizmos::gizmos::Gizmos;
///
/// fn system(mut _gizmos: Gizmos) {}
///
/// bevy::ecs::system::assert_is_system(system);
/// ```
pub struct A; I was able to use a few nightly compiler flags to show the performance of the tests, so here are the benchmarks:
|
Another thing to add: It appears |
This appears to also happen in other bevy crates such as |
running those test seems fast enough on my computer:
|
That is really weird. What compiler are you using and what OS? |
Another weird thing: Running in |
On an apple m1 max, with rust 1.74.1 |
12th Gen Intel(R) Core(TM) i7-12700H cargo test --doc
|
@doonv Can you check whether you are still experiencing this issue? |
With
It uses all 32 GB of RAM and causes the system to freeze up/soft crash after about 5-10 minutes. |
Closing as duplicate. |
What issue is this a duplicate of? |
We decided to keep the one with more info, even though it is technically newer |
Bevy version
dc8fc6c (Latest as of writing)
[Optional] Relevant system information
rustc 1.74.1 (a28077b28 2023-12-04)
What you did
Running
cargo test --doc
onbevy_gizmos
What went wrong
The doctests are extremely long. Lasting for over 60 seconds. It appears running
assert_is_system
on a system withGizmos
causes massive lag. Removingassert_is_system
makes the tests run much quicker.Additional information
I created a project that does a similar test, it ran instantly. Which is weird.
The text was updated successfully, but these errors were encountered: