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

Stop running CI on nightly? #295

Closed
gdalle opened this issue Aug 30, 2023 · 5 comments · Fixed by #374
Closed

Stop running CI on nightly? #295

gdalle opened this issue Aug 30, 2023 · 5 comments · Fixed by #374
Labels
question Further information is requested

Comments

@gdalle
Copy link
Member

gdalle commented Aug 30, 2023

It's not obvious at all that packages should run CI on nightly, for instance because it might hide actual breaking changes in the language itself. I suggest removing the nightly CI

See this discourse thread

@simonschoelly
Copy link
Member

I disagree with this - it serves as an early warning of things that might change in the future and allows one to work with Graphs.jl also on nightly. The case, that some change is only temporary is committed to nightly that breaks this package but is then removed afterwards never as far as I know never occurred for any of the packages here.

I also am not sure how this will hide breaking changes in the language itself - if that is indeed the case, then the developers of Julia should provide some kind of mechanism to disable the nightly tests on PkgEval.

@gdalle gdalle changed the title Stop running CI on nightly Stop running CI on nightly? Sep 14, 2023
@gdalle gdalle added the question Further information is requested label Sep 14, 2023
@gdalle gdalle mentioned this issue Sep 21, 2023
3 tasks
@gdalle
Copy link
Member Author

gdalle commented Sep 28, 2023

Fixed by making nightly CI failures non blocking

@gdalle gdalle closed this as completed Sep 28, 2023
@gdalle
Copy link
Member Author

gdalle commented May 4, 2024

I'd like to revisit this cause the signal sent by CI is very noisy due to nightly failures that are not always our fault. When you look at the PRs, they're all marked as failing because of nightly (the first three actually pass the tests). CI failures are not blocking for the badge on the README, but it's still a hassle for PR submitters and reviewers alike.
And again, Tim Holy himself stated that testing on nightly is a bad idea because it makes packages adapt to breaking changes instead of forcing the language updates to be non breaking (https://discourse.julialang.org/t/why-do-packages-run-continuous-integration-tests-on-julia-nightly/101208/3?u=gdalle)
@etiennedeg @simonschoelly thoughts?

image

@gdalle gdalle reopened this May 4, 2024
@etiennedeg
Copy link
Member

I don't have a strong opinion on this because each time the test fails, I check if this is nightly or not, and it's not that annoying. On the other hand, I never dig to see what is failing on nightly, so nightly tests are kinda useless for me...

@gdalle
Copy link
Member Author

gdalle commented May 4, 2024

True but it's an additional step, that may confuse infrequent contributors, and that makes it hard for us to quickly identify which PRs are ready and which are still failing just by looking at the list (since there's a red cross everywhere)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants