-
Notifications
You must be signed in to change notification settings - Fork 1
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
dev: Routinely check that the latest* package is initially installable… #42
Conversation
Test run: https://github.com/nextstrain/conda-base/actions/runs/6202996684 However, this as-is right now tests only that there exists some package version that's initially installable. It doesn't guarantee that package version is the latest. We could do that two ways:
I think (2) makes the most sense. In the meantime, testing that any version is installable is still useful, and when we update Nextstrain CLI for (2) this workflow will start always testing the latest version. |
This our intent and expectation, and it's good to be explicit about it. It may surface more installation issues, such as the one we observed in monkeypox CI¹ with the latest version not being installable, but obscuring those or surfacing them later on is _probably_ worse than addressing them head on earlier. This change will mean that any macOS 10.14 users, if any, would have to use NEXTSTRAIN_CONDA_BASE_PACKAGE="nextstrain-base ==20230615T171309Z" since newer versions aren't installable for them.² This behaviour also parallels update's behaviour since "runner.conda: Explicitly specify a nextstrain-base version when updating" (d6e4f2b). It was an oversight (on my part) to not use the same behaviour during setup, but at the time I was focused on fixing an update bug. Related-to: <nextstrain/conda-base#41> Related-to: <nextstrain/conda-base#42> ¹ <nextstrain/mpox#177> ² <nextstrain/conda-base#38>
e2091c6
to
c74a4a3
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Commit message can be updated now that nextstrain/cli#312 is merged.
…to catch issues like the one in monkeypox CI¹ earlier. Since successful installation relies on external resources out of our control, we want to regularly test it to ensure we know when an external change breaks it. Resolves <#41>. ¹ e.g. <nextstrain/mpox#177>
c74a4a3
to
a64df84
Compare
Updated. Test run worked. Merging. |
…to catch issues like the one in monkeypox CI¹ earlier. Since
successful installation relies on external resources out of our control,
we want to regularly test it to ensure we know when an external change
breaks it.
* As it stands currently, this isn't strictly the latest package, just
that there's some package version that's installable. To ensure
the former, we'd have to query the latest version (e.g. similar to
what devel/download-latest does) and pass it into setup-nextstrain-cli
as an input, which would then pass it to
nextstrain
inNEXTSTRAIN_CONDA_BASE_PACKAGE.
Alternatively, we're likely to update
nextstrain setup conda
anywayto query and install the latest version itself explicitly, just like
nextstrain update conda
does, and so this workflow can simply waitfor that change to happen.
Resolves #41.
¹ e.g. nextstrain/mpox#177
Checklist