Skip to content
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

Robustify PantsRequirementIntegrationTest. #5520

Merged
merged 1 commit into from
Feb 26, 2018

Conversation

jsirois
Copy link
Contributor

@jsirois jsirois commented 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

Copy link
Contributor

@illicitonion illicitonion left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems reasonable

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
@stuhood
Copy link
Member

stuhood commented Feb 26, 2018

Sorry about this. Thanks for fixing.

Copy link
Member

@stuhood stuhood left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This test is now more robust then our release script, heh.

@jsirois jsirois merged commit 5f25dcf into pantsbuild:master Feb 26, 2018
@jsirois jsirois deleted the issues/5519 branch February 26, 2018 18:50
stuhood pushed a commit that referenced this pull request Apr 5, 2018
### Problem

These tests were previously stabilized by running against private publishes in #5610 and #5520. But because they were still covered by `TestProjectsIntegrationTest` (outside the context of the private publish), they failed there instead.

### Solution

Ban them from `TestProjectsIntegrationTest`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants