-
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
[7.0] WASM Linux failure in DllImportSearchPathsTest: parameter 'path1' value is null #84724
Comments
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsError Blob{
"ErrorMessage": "System.ArgumentNullException: Value cannot be null. (Parameter 'path1')",
"BuildRetry": false,
"ErrorPattern": "",
"ExcludeConsoleLog": false
} Reproduction StepsFound in a dependency flow PR for 7.0. Note: This test failed in the same queue where other tests failed with the
|
Sorry, this was me - that tests loads an assembly from a file and should be disabled. I didn't hit this in my PR, which is weird. |
Created #84735. Targeting 7.0-staging. Will close/reopen once the failing test makes it there. |
Let's target staging, please. The base release branches are currently closed. Edit: This test fix goes into staging, because the actual test is in the base release branch, but it will reach staging soon. |
I'll keep this open for a couple more days just in case, but this should be resolved. |
@elinor-fung I see we have a fix for this #84735 targeting the 7.0-staging branch, but the failure was hit in release/6.0 as well: #84939 and we don't have a similar PR in 6.0-staging to disable the tests there. Can you please submit one? |
Error Blob
Reproduction Steps
Found in a dependency flow PR for 7.0.
Note: This test failed in the same queue where other tests failed with the
Nuget-Migrations
error, but this one in particular did not show that message in the output at all. Just wanted to mention it in case it could be indirectly related.Build Browser wasm Linux Release AllSubsets_Mono_RuntimeTests
Report
Summary
Known issue validation
Build: 🔎⚠️ Validation could not be done without an Azure DevOps build URL on the issue. Please add it to the "Build: 🔎" line.
Result validation:
The text was updated successfully, but these errors were encountered: