Uh oh!
There was an error while loading. Please reload this page.
move fence to the right place - #82661
Conversation
Maoni0
commented
Feb 25, 2023
/azp run runtime-coreclr gcstress-extra |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Maoni0
commented
Feb 25, 2023
all gcstress-extra tests succeeded. https://dev.azure.com/dnceng-public/public/_build/results?buildId=184780&view=results I'll run it again. |
Maoni0
commented
Feb 25, 2023
/azp run runtime-coreclr gcstress-extra |
|
No pipelines are associated with this pull request. |
Maoni0
commented
Feb 25, 2023
/azp run runtime-coreclr gcstress-extra |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Maoni0
commented
Feb 25, 2023
/azp run runtime-coreclr gcstress-extra |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Maoni0
commented
Feb 25, 2023
/azp run runtime-coreclr gcstress-extra |
|
Azure Pipelines successfully started running 1 pipeline(s). |
ghost
commented
Feb 25, 2023
Tagging subscribers to this area: @dotnet/gc |
Maoni0
commented
Feb 25, 2023
/azp run runtime-coreclr gcstress-extra |
|
Azure Pipelines successfully started running 1 pipeline(s). |
BruceForstall
commented
Feb 26, 2023
It's amazing to see gcstress-extra run clean! fwiw, the regularly scheduled run today (without your change) failed again with the same asserts on linux/arm32: https://dev.azure.com/dnceng-public/public/_build/results?buildId=185163&view=ms.vss-test-web.build-test-results-tab |
fixes#82414
we need to make sure the clearing of the syncblock and the increase of the alloc_allocated not reordered. the comment had the right idea but the implementation was incorrect. the fence should be between these 2 operations, not before the 1st one.