[main] Update dependencies from 9 repositories#54543
Conversation
[main] Update dependencies from 9 repositories - Merge branch 'main' into darc-main-b0a81754-f267-416d-a8e2-cf56f8c1ee3e - PInvoke warnings fixes for OOB assemblies - Update testPackages.proj - Update testPackages.proj - Update dependencies from https://github.com/dotnet/arcade build 20210621.1 - Merge branch 'main' into darc-main-b0a81754-f267-416d-a8e2-cf56f8c1ee3e Conflicts: eng/Version.Details.xml eng/Versions.props - Fix xml - Update dependencies from https://github.com/dotnet/xharness build 20210622.2
ghost
added
the
|
Tagging subscribers to this area: @Anipik, @safern, @ViktorHofer Issue DetailsThis is same as 04ad80a but we need to run the PR checks here
|
|
@ViktorHofer not sure if we should do this or just let Maestro handle it but then we would need to do the manual fixes again.. |
|
@premun I think opening this PR manually is fine to get to a green state again. Last time I checked, there were a lot failures that I wasn't sure of why they were happening. |
ViktorHofer
left a comment
ViktorHofer
left a comment
There was a problem hiding this comment.
Pre-approving but I expect more changes to be necessary.
|
/azp run runtime |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@premun @akoeplinger @steveisok what are all these Browser and Android failures about?? |
|
They appear to be runtime test failures. @SamMonoRT may know more. |
|
@naricc @fanyang-mono are the failures in wasm and android lanes here known ? |
|
@fanyang-mono the Android ones seem to be XHarness trying to run an app that wasn't installed before: |
|
We found the issues in WASM with @pavelsavara. It is an XHarness regression, fix coming soon |
|
One more fix - dotnet/xharness#652 |
|
I'm seeing similar restore issues in other PRs as well... |
|
@ViktorHofer the previous run in this PR was almost all green. What was failing were Android and WASM things and I think I have fixed those now so we care about the runtime tests on wasm browser, I think. But the other failures I have seen were out of my scope, so maybe if you can have a look at this build and tell? |
|
#53899 added WaitForNextTickAsync_CanceledWaitThenWaitAgain_Succeeds which is one of the failures |
|
Merging as WaitForNextTickAsync_CanceledWaitThenWaitAgain_Succeeds is known and it's the only failure |
7 participants
This is same as 04ad80a but we need to run the PR checks here