-
Notifications
You must be signed in to change notification settings - Fork 112
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
Add @test (@allocated Trixi.rhs!(du_ode, u_ode, semi, t)) to every test? #1664
Comments
Sounds reasonable to me, maybe we could move these to a separate set of allocation tests. Are there downsides you can think of (i.e., runtime, inconsistent failures, etc)? |
Runtime should not increase significantly (unless we move them to own tests, as argued by Hendrik below), as (IIRC) 75%+ test time is spent for compilation. |
Yes, this would be nice!
Moving them to a separate test job would likely have a significant impact on total test time since most time is spent in compilation. If we just include the stuff directly after testing an elixir, everything should be compiled already and the impact on total CI time should be small. |
Ok, I will start with the non-threaded tests and see how this evolves. |
Added tests (currently passing):
|
Recently, we observed allocations due to upstream/Julia changes for a variety of cases, see e.g.
#1656 , #1642, #1635 #1626.
We test for a variety of cases whether the
rhs!
allocates, see for instanceTrixi.jl/test/test_p4est_2d.jl
Lines 27 to 34 in 22856f4
Any opinions on including this for every/more tests to spot allocations faster?
The text was updated successfully, but these errors were encountered: