Repository navigation
add an import check - #191
Merged
Merged
Conversation
jwaldrop107
previously approved these changes
Sep 10, 2026
Member
Author
|
I snuck in another commit. This should fix the SIGILL in SCF by having the CI build platform-agnostic binaries (problem was the runners have different instruction sets). |
jwaldrop107
approved these changes
Sep 10, 2026
Contributor
|
🚀 [bumpr] Bumped! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The action for building our PyPI packages tests that the package builds, but never tests that the package is importable. This adds a smoke test which will try to import the package. Such a check would have caught the issue that was preventing us from having a MacOS package for SCF (issue was the package segfaulted upon importing).