Bug 1176259
Summary: | Unit tests for pulp.server.db.connection cannot be run in isolation | ||
---|---|---|---|
Product: | [Retired] Pulp | Reporter: | Randy Barlow <rbarlow> |
Component: | z_other | Assignee: | Brian Bouterse <bmbouter> |
Status: | CLOSED UPSTREAM | QA Contact: | pulp-qe-list |
Severity: | urgent | Docs Contact: | |
Priority: | high | ||
Version: | Master | CC: | bmbouter, cduryee, mhrivnak |
Target Milestone: | --- | Keywords: | Triaged |
Target Release: | 2.6.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-01-22 20:56:39 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Randy Barlow
2014-12-19 21:24:35 UTC
Raising the severity, as this could easily lead to damaging developers' databases. unassigning this bz from myself for now This is now damaging developer databases even when run with run-tests.py. A recent commit[0] seems to have shifted the order in which tests are run, and now run-tests.py will delete your development database ☹ I believe this issue is urgent severity now, as this makes it hard to "sprint" when you DB gets deleted all the time ☺ [0] https://github.com/pulp/pulp/commit/70274cf9be047708da930b25f93c9d3f4feb7f78#diff-b63946c4f3426dfd51c0a07586752ab2R325 This bug is about a specific test, but a more general method will be used to fix it. The other refactor [0] will be used to track its resolution. I'm closing this bug indicating it is being tracked upstream. [0]: https://pulp.plan.io/issues/132 |