You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Bundle_extraction_is_reused intermittently fails with "text file is busy" #44657
The Retry has logic to try 500 times (with a short sleep) and if it still fails - then throw. So unless something is really weird, then the SetLastWriteTimeUtc actually succeeded before it's done.
I don't know Linux file system enough to be able to tell if the SetLastWriteTime even requires the file to be "non-busy" - if it can work on "busy" files, then the one we call which actually modifies the content of the file is this:
I think some more info would be helpful. I'm going to try to run strace and get the syscall log to see if I can figure out what's going on under the hood here.
We'll also need to move this entire test into staging unfortunately -- it's too noisy to continue running in all PRs.
We moved the original stuff to the staging branch, must have missed it on alpine. @VSadov is seeing if he can succeed where I failed -- if we don't have any ideas we can move this one to staging as well.
Activity
Dotnet-GitSync-Bot commentedon Nov 13, 2020
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.
eerhardt commentedon Dec 9, 2020
This failed again here:
https://dev.azure.com/dnceng/public/_build/results?buildId=913629&view=logs&j=488ba465-33f8-5af3-b422-ec6526547df5&t=6c6997ae-4d39-5a90-21e3-089719c051c1&l=525
https://dev.azure.com/dnceng/public/_build/results?buildId=913629&view=ms.vss-test-web.build-test-results-tab&runId=29085272&resultId=100002&paneView=debug
vitek-karas commentedon Dec 9, 2020
The last thing we do on the executable before we call
Process.Start(which fails) is this:runtime/src/installer/managed/Microsoft.NET.HostModel/AppHost/HostWriter.cs
Lines 175 to 177 in dbe5e2a
The Retry has logic to try 500 times (with a short sleep) and if it still fails - then throw. So unless something is really weird, then the
SetLastWriteTimeUtcactually succeeded before it's done.I don't know Linux file system enough to be able to tell if the SetLastWriteTime even requires the file to be "non-busy" - if it can work on "busy" files, then the one we call which actually modifies the content of the file is this:
runtime/src/installer/managed/Microsoft.NET.HostModel/AppHost/BinaryUtils.cs
Lines 68 to 74 in dbe5e2a
This has usings around the right stuff - so it should close the file once it's done.
eerhardt commentedon Dec 11, 2020
Failed again here:
https://dev.azure.com/dnceng/public/_build/results?buildId=916830&view=logs&j=488ba465-33f8-5af3-b422-ec6526547df5&t=6c6997ae-4d39-5a90-21e3-089719c051c1&l=536
https://dev.azure.com/dnceng/public/_build/results?buildId=916830&view=ms.vss-test-web.build-test-results-tab&runId=29156076&resultId=100011&paneView=debug
agocke commentedon Dec 11, 2020
I think some more info would be helpful. I'm going to try to run
straceand get the syscall log to see if I can figure out what's going on under the hood here.We'll also need to move this entire test into staging unfortunately -- it's too noisy to continue running in all PRs.
Disable apphost tests on Linux
danmoseley commentedon Dec 14, 2020
Failed again https://dev.azure.com/dnceng/public/_build/results?buildId=920007&view=logs&jobId=a45ba455-ebc4-599b-2570-d14d0585f433
radical commentedon Dec 14, 2020
Failed here - https://dev.azure.com/dnceng/public/_build/results?buildId=920677&view=ms.vss-test-web.build-test-results-tab&runId=29254050&resultId=100009&paneView=debug
Disable apphost tests on Linux (#45976)
directhex commentedon Mar 3, 2021
Closing, fixed by #45976
4 remaining items
safern commentedon Apr 6, 2021
Reopening as this is on the runtime-staging pipeline.
VincentBu commentedon May 24, 2021
Failed in runtime 20210523.14
Failed test:
Error message:
VincentBu commentedon Jun 3, 2021
Failed again in runtime 20210602.73
Failed test:
Error message:
danmoseley commentedon Jun 3, 2021
@agocke we seem to be continuing to hit this (I think there is another issue as well)
agocke commentedon Jun 3, 2021
We moved the original stuff to the staging branch, must have missed it on alpine. @VSadov is seeing if he can succeed where I failed -- if we don't have any ideas we can move this one to staging as well.
agocke commentedon Aug 30, 2021
Duplicate of #53587