Enable GPU compatibility check in CI

[huiyuxie]

This workflow will pass for Julia 1.10 but fail for Julia 1.11 so I restrict the test only to 1.10

[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 with its PR number.

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 96.37%. Comparing base (824f7a8) to head (03b7bc4).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2168   +/-   ##
=======================================
  Coverage   96.37%   96.37%           
=======================================
  Files         483      483           
  Lines       38333    38333           
=======================================
  Hits        36943    36943           
  Misses       1390     1390           

Flag	Coverage Δ
unittests	96.37% <ø> (ø)

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.

[huiyuxie]

I need thorough tests on all available OS x architecture. This will increase CI time, but it is necessary to ensure compatibility across all available resources.

[huiyuxie]

Review please @ranocha Thanks!

[huiyuxie]

Is it really? You just activate an empty temporary environment and add CUDA.jl to it, so it does not do anything with Trixi.jl, does it?

Yes 😥 - I aimed to create an independent environment for each but forgot it is empty.

[huiyuxie]

Is the codecov issue fixed? The CI looks quite normal to me

[huiyuxie]

May I ask why we do not include tests for the 32 bit archs in the general CI? - Julia supports 32 bit on Linux and Windows

[ranocha]

May I ask why we do not include tests for the 32 bit archs in the general CI? - Julia supports 32 bit on Linux and Windows

The platforms are not used very often. Testing them in detail would add a huge amount of additional CI time.

[ranocha]

Thanks

[ranocha]

I just noticed this - the name can be misleading since it does not perform any GPU compatibility tests running simulation etc.