Issue #1135
closed
Pulp's unit tests are not compatible with Mock>=1.1.0
Description
A new version of Mock was recently released that breaks compatibility with the version that Pulp had been using before (1.0.1). A bug has been filed about this with Mock[0], but may not be fixed. We should update Pulp's usages of Mock so that we are compliant with their new API.
[0] https://github.com/testing-cabal/mock/issues/263
- Priority changed from Normal to High
- Triaged changed from No to Yes
High priority to be sure we keep checking on the status of this upstream. When fixed, we need to remove our restriction on 1.0.1 in test_requirements and puppet module etc. And, verify Jenkins builds.
- Status changed from NEW to ASSIGNED
- Assignee set to amacdona@redhat.com
- Blocked by Task #931: Investigate and develop a plan for Pulp to use Software Collections added
- Status changed from ASSIGNED to NEW
- Assignee deleted (
amacdona@redhat.com)
- Status changed from NEW to CLOSED - WONTFIX
Pulp 2 is approaching maintenance mode, and this Pulp 2 ticket is not being actively worked on. As such, it is being closed as WONTFIX. Pulp 2 is still accepting contributions though, so if you want to contribute a fix for this ticket, please reopen or comment on it. If you don't have permissions to reopen this ticket, or you want to discuss an issue, please reach out via the developer mailing list.
Also available in: Atom
PDF
Pin the version of Mock that we use.
Pulp uses Mock in a way that is now broken[0] with the new version that was recently released. This commit pins us to use Mock<1.1 to avoid the problem for now. In the end, we should update our tests to use the new Mock API as part of the work on issue #1135.
[0] https://github.com/testing-cabal/mock/issues/263
re #1135