-
-
Notifications
You must be signed in to change notification settings - Fork 652
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
PantsRequirementIntegrationTest
breaks for pants dep changes
#5519
Labels
Comments
jsirois
added a commit
to jsirois/pants
that referenced
this issue
Feb 26, 2018
Previously changes to `pantsbuild.pants` requirements on master between releases would leave to resolution conflicts in the `test_pants_requirement` test. Make the test robust to these sort of changes by producing and consuming a unique `pantsbuild.pants` distribution for each run of the test. Fixes pantsbuild#5519
jsirois
added a commit
to jsirois/pants
that referenced
this issue
Feb 26, 2018
Previously changes to `pantsbuild.pants` requirements on master between releases would lead to resolution conflicts in the `test_pants_requirement` test. Make the test robust to these sort of changes by producing and consuming a unique `pantsbuild.pants` distribution for each run of the test. Fixes pantsbuild#5519
jsirois
added a commit
that referenced
this issue
Feb 26, 2018
Previously changes to `pantsbuild.pants` requirements on master between releases would lead to resolution conflicts in the `test_pants_requirement` test. Make the test robust to these sort of changes by producing and consuming a unique `pantsbuild.pants` distribution for each run of the test. Fixes #5519
jsirois
added a commit
to jsirois/pants
that referenced
this issue
Mar 17, 2018
Previously, when the pants `VERSION` was bumped and before publishing the `test_setup_py_unregistered_pants_plugin` test would fail to resolve `pantsbuild.pants` at the new version on pypi. Update the test to use a custom-produced `pantsbuild.pants` distribution and share this logic with `PantsRequirementIntegrationTest`. Similar to pantsbuild#5519
jsirois
added a commit
that referenced
this issue
Mar 17, 2018
Previously, when the pants `VERSION` was bumped and before publishing the `test_setup_py_unregistered_pants_plugin` test would fail to resolve `pantsbuild.pants` at the new version on pypi. Update the test to use a custom-produced `pantsbuild.pants` distribution and share this logic with `PantsRequirementIntegrationTest`. Similar to #5519
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The test exercises the
pants_requirement
target on master where we maintain a pants version of, say1.5.0.dev4
across many commits. If any of those commits mutates requirements forpantsbuild.pants
then our resolution assumption that a version always resolves stably is broken. This leads to a broken test along these lines:The text was updated successfully, but these errors were encountered: