CI macOS: Build following stages even when some job failed; adjust platforms#36711
CI macOS: Build following stages even when some job failed; adjust platforms#36711vbraun merged 3 commits intosagemath:developfrom
Conversation
… of the jobs failed
…tandard by -minimal, to avoid problem with maxima
…void problems with optional conda packages
|
Documentation preview for this PR (built with commit a933ae2; changes) is ready! 🎉 |
|
What are stages 1 and 2? I have a guess about |
|
Stage 1 builds non-Python packages, stage 2 builds Python packages |
| with: | ||
| stage: "2" | ||
| needs: [stage-1] | ||
| if: ${{ success() || failure() }} |
There was a problem hiding this comment.
Is this equivalent to if: ${{ always() }}? (I found that at https://docs.github.com/en/actions/using-jobs/using-jobs-in-a-workflow#example-not-requiring-successful-dependent-jobs.) Any reason to prefer one approach to the other?
There was a problem hiding this comment.
We just got rid of a lot of always() in:
|
Okay, looks good. |
|
Thanks! Setting it to blocker so it gets merged in the next rc |
<!-- ^^^^^ Please provide a concise, informative and self-explanatory title. Don't put issue numbers in there, do this in the PR body below. For example, instead of "Fixes sagemath#1234" use "Introduce new method to calculate 1+1" --> <!-- Describe your changes here in detail --> sagemath#36711 introduced a syntax error that causes failures: https://github.com/sagemath/sage/actions/runs/6870325982 Fixed here - as seen in https://github.com/mkoeppe/sage/actions/runs/6874334555 <!-- Why is this change required? What problem does it solve? --> <!-- If this PR resolves an open issue, please link to it here. For example "Fixes sagemath#12345". --> <!-- If your change requires a documentation PR, please link it appropriately. --> ### 📝 Checklist <!-- Put an `x` in all the boxes that apply. --> <!-- If your change requires a documentation PR, please link it appropriately --> <!-- If you're unsure about any of these, don't hesitate to ask. We're here to help! --> <!-- Feel free to remove irrelevant items. --> - [x] The title is concise, informative, and self-explanatory. - [x] The description explains in detail what this PR is about. - [ ] I have linked a relevant issue or discussion. - [ ] I have created tests covering the changes. - [ ] I have updated the documentation accordingly. ### ⌛ Dependencies <!-- List all open PRs that this PR logically depends on - sagemath#12345: short description why this is a dependency - sagemath#34567: ... --> <!-- If you're unsure about any of these, don't hesitate to ask. We're here to help! --> URL: sagemath#36723 Reported by: Matthias Köppe Reviewer(s): John H. Palmieri
To fix what can be seen in https://github.com/sagemath/sage/actions/runs/6827163283 - stage-2 was not attempted because some of the stage-1 jobs failed.
We also replace one of the failing platforms and remove another.
📝 Checklist
⌛ Dependencies