Opened 5 years ago
Closed 5 years ago
#31168 closed New feature (wontfix)
Add ability to mark test as parallel unsafe.
| Reported by: | Stuart Axon | Owned by: | nobody |
|---|---|---|---|
| Component: | Testing framework | Version: | dev |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
I'd like to run use --parallel, but my website uses TreeBeard (via django cms), where some operations fail due to a race condition under parallel operation.
I don't see a fix any time soon in DCMS's future, but this can't be the only library with a similar issue.
It would be good if I could mark a test as @parallel_unsafe so that the rest of the tests could run in parallel, while all the parallel_unsafe tests would be guaranteed to run one at a time.
Change History (1)
comment:1 by , 5 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
| Summary: | Add ability to mark test as parallel unsafe → Add ability to mark test as parallel unsafe. |
| Version: | 3.0 → master |
Note:
See TracTickets
for help on using tickets.
You can Enforce running test classes sequentially. I don't think that marking a single test as "parallel unsafe" is necessary and doable.