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

Use nightly tests in CI #281

Closed
beorostica opened this issue Jan 4, 2024 · 2 comments · Fixed by #277
Closed

Use nightly tests in CI #281

beorostica opened this issue Jan 4, 2024 · 2 comments · Fixed by #277
Assignees

Comments

@beorostica
Copy link
Contributor

beorostica commented Jan 4, 2024

The idea is to regularly test with the Julia nightly version (the latest version under development) to avoid surprises when a new Julia version is released

@beorostica beorostica self-assigned this Jan 4, 2024
@beorostica beorostica moved this to Todo in KomaMRI.jl v0.8.0 Jan 4, 2024
@beorostica beorostica moved this from Todo to In Progress in KomaMRI.jl v0.8.0 Jan 8, 2024
@beorostica
Copy link
Contributor Author

We aim to test both stable Julia and nightly Julia. However, if the nightly build fails while the stable build passes, we would like to generate a 'ticket' for the entire CI process and a 'warning' to indicate that the 'nightly' build is not successful.

Unfortunately, it seems that this feature is not currently implemented in GitHub Actions. You can refer to actions/runner#2347 for more information.

@beorostica
Copy link
Contributor Author

For the time being, we have configured the following settings:

  • We use the if: always() statement for stable tests.
  • For nightly tests, we employ the continue-on-error: true statement.

This configuration allows for the scenario where the nightly tests consistently pass (it displays a 'ticket'), while the stable tests may either throw an error or pass. In both cases, all tests for the submodules are executed. It is crucial to regularly inspect the log messages of the nightly tests because the passed 'ticket' in this case doesn't provide much information.

@beorostica beorostica linked a pull request Jan 10, 2024 that will close this issue
@github-project-automation github-project-automation bot moved this from In Progress to Solved in Dev in KomaMRI.jl v0.8.0 Jan 10, 2024
@beorostica beorostica moved this from Solved in Dev to Solved in Stable in KomaMRI.jl v0.8.0 Jan 19, 2024
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

Successfully merging a pull request may close this issue.

1 participant