Lock state before we modify.#2795
Conversation
When we start a container we lock state, we should do the same in stop. Detected via -race.
|
We probably want to start using |
|
LGTM |
|
LGTM, thanks |
…t-race Lock state before we modify.
|
This broke the build |
|
@vieux looking at failure. But feel free to revert this. |
|
@pnasrat Is this a local build or on the CI ? |
|
I ran the tests and there were no issues. |
tianon points out it may just be another flaky test due to another race Paul On 21 November 2013 14:40, Michael Crosby [email protected] wrote:
|
|
same here I didn't get any issue |
|
The following tests are failing for me: |
|
@unclejack out of curiosity how many cores on the machine you're testing on? |
|
@pnasrat It's a VM with 3 cores. |
|
I can reproduce some of the failures that @unclejack is seeing. I opened a PR to revert this change. It looks like we have found one of the destinations of the races in the code base here. |
|
I'll spend some more time on getting this fixed Monday. |
When we start a container we lock state, we should do the same in stop.
Detected via -race.
See Issue #713