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

CI gets stuck when running whole test suite but works when run in individually #225

Open
agoscinski opened this issue Aug 14, 2024 · 0 comments

Comments

@agoscinski
Copy link
Contributor

agoscinski commented Aug 14, 2024

In the CI file had to

                pytest -v tests --cov --durations=0

split into

                pytest -m "not frontend and not backend" -v --cov --durations=0
                pytest -m backend -v --cov-append --durations=0
                pytest -m frontend -v --cov-append --durations=0

in RP #221 because the test suite got stuck when running the frontend tests.

agoscinski added a commit that referenced this issue Aug 14, 2024
Implements requested tests in issue #159.

Backend and frontend tests now use their own dedicated aiida profile to avoid
changes in the aiida database that might affect the tests. For that they have
been moved to their own module folder.

Frontend tests reuse ran aiida workgraph calculation to save time.

CI tests have been splitted into three runs of pytest (see issue #225)
agoscinski added a commit that referenced this issue Aug 14, 2024
* Implements requested tests in issue #159.

* Backend and frontend tests now use their own dedicated aiida profile to avoid
changes in the aiida database that might affect the tests. For that they have
been moved to their own module folder.

* Frontend tests reuse ran aiida workgraph calculation to save time.

* CI tests have been splitted into three runs of pytest (see issue #225)
agoscinski added a commit that referenced this issue Aug 14, 2024
* Implements requested tests in issue #159.

* Backend and frontend tests now use their own dedicated aiida profile to avoid
changes in the aiida database that might affect the tests. For that they have
been moved to their own module folder.

* Frontend tests reuse ran aiida workgraph calculation to save time.

* CI tests have been splitted into three runs of pytest (see issue #225)
agoscinski added a commit that referenced this issue Aug 14, 2024
* Implements requested tests in issue #159.

* Backend and frontend tests now use their own dedicated aiida profile to avoid
changes in the aiida database that might affect the tests. For that they have
been moved to their own module folder.

* Frontend tests reuse ran aiida workgraph calculation to save time.

* CI tests have been splitted into three runs of pytest (see issue #225)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant