Repository navigation
Precondition failure: File has not had execution verified #79439
Copy link
Copy link
Closed
Labels
Known Build ErrorUse this to report build issues in the .NET Helix tabUse this to report build issues in the .NET Helix tabarea-Interop-coreclrblocking-clean-ciBlocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'blocking-clean-ci-optionalBlocking optional rolling runsBlocking optional rolling runs
Description
Build Information
Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=106998
Build error leg or test failing: ComInterfaceGenerator.Unit.Tests.WorkItemExecution
Pull request: #79433
Error Message
Fill the error message using known issues guidance.
{
"ErrorMessage": "Precondition failure: File has not had execution verified",
"BuildRetry": false
}Report
Summary
| 24-Hour Hit Count | 7-Day Hit Count | 1-Month Count |
|---|---|---|
| 2 | 53 | 230 |
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Known Build ErrorUse this to report build issues in the .NET Helix tabUse this to report build issues in the .NET Helix tabarea-Interop-coreclrblocking-clean-ciBlocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'blocking-clean-ci-optionalBlocking optional rolling runsBlocking optional rolling runs
Activity
MichalStrehovsky commentedon Dec 9, 2022
MichalStrehovsky commentedon Dec 9, 2022
@elinor-fung could this be Fusion's revenge for #79380?
elinor-fung commentedon Dec 10, 2022
I think it is #79341 - @jakobbotsch
Test hitting this added in #77130 (PR build was before #79341 went in) - cc @jkoritzinsky
jakobbotsch commentedon Dec 10, 2022
@elinor-fung Why do you think it is related to #79341? It doesn't immediately strike me as being related.
The failing configuration is release libraries with checked coreclr on win-x64. It looks like that configuration was skipped in the CI run for #77130 which might explain it.
elinor-fung commentedon Dec 10, 2022
Ah, sorry, my bad. I checked that it wasn't #79380 and just skimmed through recent changes - thought it stopped happening without #79341, but I must have been confused (just looked again). Totally missed that that leg was skipped in #77130.
jkoritzinsky commentedon Dec 10, 2022
#78580 might also be related as the lowest managed frame was added in #78580 and that was merged recently as well.
BruceForstall commentedon Dec 15, 2022
@elinor-fung @dotnet/interop-contrib Any progress on this one? I've seen this fail in a lot of pipelines today.
danmoseley commentedon Dec 15, 2022
Cc @stephentoub
jkotas commentedon Dec 24, 2022
Standalone repro:
Program.cs
MyEnum.cs - compile into separate .dll
Delete token scanning from JIT/EE interface
Delete token scanning from JIT/EE interface (#79964)