This solves #24 in one sense, by stopping runs from interfering with one another. Each waits patiently and retries after 2s if there's another run already accessing/changing tables.
Don't merge if not the correct solution!!
Under this change, all runs after run=1 are essentially working across two databases - root and mutirunId folders. Is this expected?
This solves #24 in one sense, by stopping runs from interfering with one another. Each waits patiently and retries after 2s if there's another run already accessing/changing tables.
Don't merge if not the correct solution!!
Under this change, all runs after run=1 are essentially working across two databases - root and mutirunId folders. Is this expected?