Repository navigation
History files are overwritten by concurrent builds #187
Description
My understanding is that the history file is only loaded at the beginning, and then overwritten at the end. This means that when running tests concurrently on the same machine, long running builds will always win over all the others (it's a sort of TOCTOU problem). I see two options:
- update, with a lock file, the history file instead of assuming it didn't change since the beginning of the tests
- provide a mechanism to separate the history files, for example with yet another keyword argument to use as prefix for the file.
Activity
Add a `history_key` keyword to keep separate test histories
Add a `history_key` keyword to keep separate test histories
Update the test history under a lock, in batches of finished tests
Add a `history_key` keyword to keep separate test histories
Add a `history_key` keyword to keep separate test histories
Update the test history under a lock, in batches of finished tests
Add a `history_key` keyword to keep separate test histories
Add a `history_key` keyword to keep separate test histories (#189)