-
Notifications
You must be signed in to change notification settings - Fork 2.5k
test: cover build config-settings and missing backend warning #11007
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
Open
Shriprasad-P
wants to merge
2
commits into
python-poetry:main
Choose a base branch
from
Shriprasad-P:test/build-command-coverage
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+37
−0
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
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.
suggestion (testing): Strengthen
--config-settings local-versioncoverage by asserting artifact names include the local version labelThis test currently only verifies that some artifacts exist for the glob from
get_package_glob, but not that the local version label is actually present in their filenames. Ifget_package_globbecame too permissive, the test could still pass while ignoring the local version. Please add an assertion (e.g.assert all(local_version_label in archive.name for archive in build_artifacts)) to directly verify artifact naming and better protect against regressions.Suggested implementation:
This change assumes:
build_artifactsis defined earlier intest_build_with_config_settings_local_versionas an iterable of artifact paths.local_version_labelis the string used in the--config-settings local-version=...invocation.If either name differs in your actual file, please adjust the assertion to match the existing variable names.