Use serial_test #469
Labels
No labels
A: API
A: Backend
A: Federation
A: Front-End
A: I18N
A: Meta
A: Security
Build
C: Bug
C: Discussion
C: Enhancement
C: Feature
Compatibility
Dependency
Design
Documentation
Good first issue
Help welcome
Mobile
Rendering
S: Blocked
S: Duplicate
S: Incomplete
S: Instance specific
S: Invalid
S: Needs Voting/Discussion
S: Ready for review
Suggestion
S: Voted on Loomio
S: Wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Plume/Plume#469
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This crate allows you to run some test one after the other. By using it we could make sure database tests are always run serially (without even needing to set
RUST_TEST_THREADS=1
), and other tests can still run concurrently.Plume version (and/or commit): 0.2.0
why are our database tests not parallelizable?
fixing that issue would be a better solution than cheating on the database tests
I agree, and I don't remember the details… 😅 maybe @fdb-hiroshima knows, since she is the one who wrote most of these tests.
I have no idea, running theme in parallel on my computer (or anything other than Travis really) works fine, but for some reasons, it did not work at all on Travis, one random test was passing, and all others failed
Ah, they don't work concurrently on my computer either… Really weird 🤷♀️
so, when looking into deploying Plume, please consider doing it on @fdb-hiroshima's machine, but not on Travis (docker!) or on @BaptisteGelez's machine.
(Plume is using virtual machines from GCE, not docker containers when building on Travis)