Improve test lock usage pattern

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Gone away
    • Priority: Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      We currently run our tests in parallel and use a test lock to avoid interference. Although we've determined that running sequentially is infeasible at this time, we should consider improving the way we use the test lock to avoid the pitfalls described in RUST-1280. Potential solutions include using the serial crate and introducing a macro/proc macro that acquires the lock.

            Assignee:
            Unassigned
            Reporter:
            Isabel Atkinson
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: