-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[browser][wbt] fails with InvalidOperationException: There is no currently active test
#105315
Comments
Tagging subscribers to this area: @dotnet/area-infrastructure-libraries |
Tagging subscribers to this area: @directhex, @matouskozak |
I'm not able to reproduce it locally. It doesn't seem related to fingerprinting. |
NoFingerprint
wbt fails with InvalidOperationException
InvalidOperationException: There is no currently active test
@mkhamoyan Can you please look into this one? It's quite low priority (if don't start happening more often, but it doesn't seem so far). The exception comes from |
Note for the future: unsubscribing from the handlers did not fully fix the issue, the last 2 hits are on PRs created after the fix was merged. |
Following the stack:
We might be trying to |
Sample log:
All the available failure logs are from Linux. |
The last 2 hits are on PRs that had the #108319 change. It's still unfixed |
Build Information
Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=751591
Build error leg or test failing: Workloads-NoWebcil-NoFingerprint-ST-Wasm.Build.Tests.WorkItemExecution
Pull request: #105302
Error Message
Fill the error message using step by step known issues guidance.
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=751591
Error message validated:
[Unhandled exception. System.InvalidOperationException: There is no currently active test.
]Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 7/23/2024 1:57:11 PM UTC
Report
Summary
The text was updated successfully, but these errors were encountered: