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

shift AtomicConfigNumber to standard unit tests #5176

Conversation

BrianMarre
Copy link
Member

@BrianMarre BrianMarre commented Oct 18, 2024

moves the atomicConfigNumber unit test of FLYonPIC from it's custom location to the standard unit test folder of PIConGPU and makes it part of the the unit test suite of PIConGPU.

@attention This PR removes the picongpu::configNumber::RUN_UNIT_TEST option in the atomicPhysics_Debug.param file. Old setups setting with this option will still work, but any setting of the option will be ignored.

If you want to run this test, use the PIConGPU unit test framework instead.

ci: picongpu

@BrianMarre BrianMarre force-pushed the topic-moveAtomicPhysicsUnittestToCIUnitTests branch from 1890c3e to 5ddb8f9 Compare October 21, 2024 08:37
@psychocoderHPC psychocoderHPC added this to the 0.8.0 / Next stable milestone Oct 21, 2024
@psychocoderHPC psychocoderHPC added refactoring code change to improve performance or to unify a concept but does not change public API component: tests unit tests labels Oct 21, 2024
Copy link
Contributor

@chillenzer chillenzer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As planned, this is not yet properly integrated into Catch2 and I believe to leverage its full potential, we should do so at some point. I have opened #5186 to track this.

@chillenzer chillenzer merged commit 6347d31 into ComputationalRadiationPhysics:dev Oct 22, 2024
10 checks passed
@BrianMarre BrianMarre deleted the topic-moveAtomicPhysicsUnittestToCIUnitTests branch October 22, 2024 11:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: tests unit tests refactoring code change to improve performance or to unify a concept but does not change public API
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants