Bug: Concurrency Issue with Environment Information File Lock #275
Description
Quick Description
When adding the environment information we use a file lock, to ensure flawless concurrent access. This however has a bug when parallel file access is performed.
Actual Behaviour
If there are parallel test runs, the file lock might be null, which leads to a breaking test case. Also data might be overwritten currently.
Expected Behaviour
If there are parallel test runs, the environment information from both runs will be added but no duplicates are written.
Tasks
- Ensure file access is concurrency safe, even if several JVMs run in parallel.
- Make sure file content is not just overwritten, but merged.
- Note: If several threads use the same key/value just add it once, if key OR value differs, add both. Also if the File lock is active we currently just drop the other files.