Skip to content

[6.0-staging] Disable DllImportSearchPathsTest in mobile #86576

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

Merged
merged 1 commit into from
May 23, 2023

Conversation

akoeplinger
Copy link
Member

@akoeplinger akoeplinger commented May 22, 2023

Loading assemblies from subdirectories is not supported, this ports the fix from main to 6.0

Fixes #86271

@akoeplinger akoeplinger requested a review from steveisok May 22, 2023 09:55
@ghost ghost added the area-Interop-coreclr label May 22, 2023
@ghost ghost assigned akoeplinger May 22, 2023
@akoeplinger
Copy link
Member Author

This is a test-only change so no tactics approval necessary.

@ghost
Copy link

ghost commented May 22, 2023

Tagging subscribers to this area: @directhex
See info in area-owners.md if you want to be subscribed.

Issue Details

Loading assemblies from subdirectories is not supported, this ports the fix from main to 6.0 Fixes #86271

Author: akoeplinger
Assignees: akoeplinger
Labels:

Servicing-approved, area-Infrastructure-mono

Milestone: -

Loading assemblies from subdirectories is not supported, this ports the fix from main to 6.0
Fixes #86271
@carlossanlop
Copy link
Contributor

Loading assemblies from subdirectories is not supported, this ports the fix from main to 6.0

Do we need a similar PR for 7.0?

@akoeplinger akoeplinger merged commit c5fea1b into release/6.0-staging May 23, 2023
@akoeplinger akoeplinger deleted the fix-test branch May 23, 2023 06:09
@akoeplinger
Copy link
Member Author

Do we need a similar PR for 7.0?

Not really, in main/7.0 this job runs in runtime-extra-platforms which doesn't get triggered automatically.

@carlossanlop
Copy link
Contributor

Not really, in main/7.0 this job runs in runtime-extra-platforms which doesn't get triggered automatically

But if someone triggers runtime-extra-platforms in 7.0, they'll hit the failure, right?

@akoeplinger
Copy link
Member Author

Yes. Let me backport to 7.0 as well so we're good there too.

@akoeplinger
Copy link
Member Author

/backport to release/7.0-staging

@github-actions
Copy link
Contributor

Started backporting to release/7.0-staging: https://github.com/dotnet/runtime/actions/runs/5069357570

@github-actions
Copy link
Contributor

@akoeplinger backporting to release/7.0-staging failed, the patch most likely resulted in conflicts:

$ git am --3way --ignore-whitespace --keep-non-patch changes.patch

Applying: [6.0] Disable DllImportSearchPathsTest in mobile
Using index info to reconstruct a base tree...
M	src/tests/Interop/DllImportSearchPaths/DllImportSearchPathsTest.cs
M	src/tests/issues.targets
Falling back to patching base and 3-way merge...
Auto-merging src/tests/issues.targets
CONFLICT (content): Merge conflict in src/tests/issues.targets
Auto-merging src/tests/Interop/DllImportSearchPaths/DllImportSearchPathsTest.cs
CONFLICT (content): Merge conflict in src/tests/Interop/DllImportSearchPaths/DllImportSearchPathsTest.cs
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 [6.0] Disable DllImportSearchPathsTest in mobile
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
Error: The process '/usr/bin/git' failed with exit code 128

Please backport manually!

@github-actions
Copy link
Contributor

@akoeplinger an error occurred while backporting to release/7.0-staging, please check the run log for details!

Error: git am failed, most likely due to a merge conflict.

@akoeplinger
Copy link
Member Author

#86708

akoeplinger added a commit to akoeplinger/runtime that referenced this pull request May 24, 2023
@ghost ghost locked as resolved and limited conversation to collaborators Jun 23, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[6.0] [Android] CI failure: Interop_DllImportSearchPaths - Non-success instrumentation exit code: 101, expected: 100
3 participants