WIP: check CI on Julia v1.11 pre-release version

[sloede]

No description provided.

[github-actions]

Review checklist

This checklist is meant to assist creators of PRs (to let them know what reviewers will typically look for) and reviewers (to guide them in a structured review process). Items do not need to be checked explicitly for a PR to be eligible for merging.

Purpose and scope

• The PR has a single goal that is clear from the PR title and/or description.
• All code changes represent a single set of modifications that logically belong together.
• No more than 500 lines of code are changed or there is no obvious way to split the PR into multiple PRs.

Code quality

• The code can be understood easily.
• Newly introduced names for variables etc. are self-descriptive and consistent with existing naming conventions.
• There are no redundancies that can be removed by simple modularization/refactoring.
• There are no leftover debug statements or commented code sections.
• The code adheres to our conventions and style guide, and to the Julia guidelines.

Documentation

• New functions and types are documented with a docstring or top-level comment.
• Relevant publications are referenced in docstrings (see example for formatting).
• Inline comments are used to document longer or unusual code sections.
• Comments describe intent ("why?") and not just functionality ("what?").
• If the PR introduces a significant change or new feature, it is documented in NEWS.md.

Testing

• The PR passes all tests.
• New or modified lines of code are covered by tests.
• New or modified tests run in less then 10 seconds.

Performance

• There are no type instabilities or memory allocations in performance-critical parts.
• If the PR intent is to improve performance, before/after time measurements are posted in the PR.

Verification

• The correctness of the code was verified using appropriate tests.
• If new equations/methods are added, a convergence test has been run and the results
  are posted in the PR.

Created with ❤️ by the Trixi.jl community.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 66.29%. Comparing base (b1a84a6) to head (a54a3e5).
Report is 165 commits behind head on main.

❗ There is a different number of reports uploaded between BASE (b1a84a6) and HEAD (a54a3e5). Click for more details.

HEAD has 4 uploads less than BASE

Flag	BASE (b1a84a6)	HEAD (a54a3e5)
unittests	24	20

Additional details and impacted files

@@             Coverage Diff             @@
##             main    #1904       +/-   ##
===========================================
- Coverage   96.12%   66.29%   -29.84%     
===========================================
  Files         448      448               
  Lines       36081    36005       -76     
===========================================
- Hits        34682    23866    -10816     
- Misses       1399    12139    +10740     

Flag	Coverage Δ
unittests	66.29% <ø> (-29.84%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[sloede]

We get errors about overwritten methods, e.g., in the log here or here.

The problem seems to be multiple includes of the same function definition, e.g., when looping over setups (first case) or just reusing a setup with an explicit include (the second case).

Any idea how this can be easily fixed? For example, would it be possible (sensible) that we create a separate (anonymous?) Julia module upon each invocation of test_trixi_include?

[sloede]

Ah, I see that @ranocha had the idea of anonymous modules before, but that they do not work with our structured, curvilinear files 😢

Trixi.jl/test/test_trixi.jl

Lines 205 to 213 in b1a84a6

	# TODO: `@eval` is evil
	# We would like to use
	# mod = gensym(name)
	# ...
	# module $mod
	# to create new module names for every test set. However, this is not
	# compatible with the dirty hack using `@eval` to get the mapping when
	# loading structured, curvilinear meshes. Thus, we need to use a plain
	# module name here.

Any other ideas how to proceed?

[ranocha]

Let's just include warnings like

"WARNING: Method definition pretty_form_utf(Base.Val{:energy_potential}) in module TrixiTestModule at /home/runner/work/Trixi.jl/Trixi.jl/examples/paper_self_gravitating_gas_dynamics/elixir_eulergravity_jeans_instability.jl:121 overwritten in module TrixiTestModule on the same line (check for duplicate calls to `include`)

in the list of ignored warnings?

[sloede]

Let's just include warnings like

"WARNING: Method definition pretty_form_utf(Base.Val{:energy_potential}) in module TrixiTestModule at /home/runner/work/Trixi.jl/Trixi.jl/examples/paper_self_gravitating_gas_dynamics/elixir_eulergravity_jeans_instability.jl:121 overwritten in module TrixiTestModule on the same line (check for duplicate calls to `include`)

in the list of ignored warnings?

Won't we risk hiding real errors with this? But in general, I do like the idea due to its simplicity 👍

[ranocha]

Superseded by #1993