Add pip-only install/CLI smoke test #456
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
References
Code changes
Adds a
pip
-only install test to CI (doesn't even do a checkout). By making these rely onlint
andbuild
, I'm hoping the acceptance jobs start first, so that this doesn't add to the bottom-line wall-clock time... even still, may want to cache pip, etc.The existing
pip check
in the acceptance job is still good to keep, as we want to know if our test dependencies have drifted or conflict with each other.Ideally we'd just install the
jupyterlab-lsp
tarball, to ensure theinstall_requires
is configured properly, but I don't know how to make pip do that and not pull in old versions of a locally-built dependency.User-facing changes
N/A, but should help non-dev installs go more smoothly.
Backwards-incompatible changes
N/A
Chores