-
Notifications
You must be signed in to change notification settings - Fork 2.6k
[release/3.1] Update dependencies from dotnet/corefx #28179
[release/3.1] Update dependencies from dotnet/corefx #28179
Conversation
…608.1 Microsoft.Private.CoreFx.NETCoreApp From Version 4.7.0-servicing.20460.1 -> To Version 4.7.0-servicing.21308.1
…610.1 Microsoft.Private.CoreFx.NETCoreApp From Version 4.7.0-servicing.20460.1 -> To Version 4.7.0-servicing.21310.1
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
Tests are totally broken on several configs, eg.,
@wtgodbe @Anipik is this a mismatch in versioning between the repos somehow related to branding? |
Yeah, I think this will be unblocked once the update from core-setup is in |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
@danmoseley @jeffschwMSFT lots of tests failures here that look new, can someone take a look? e.g. System.Diagnostics.Tests.DebuggerDisplayAttributeTests.Target_SetNull_ThrowsArgumentNullException |
@wtgodbe will do. I am seeing a lot of test build breaks. Do those fit within the expected? (I will ask that we follow-up to get those resolved). |
I don't remember seeing those build breaks before, though admittedly I'm not as familiar with this build infra as I used to be. |
I have asked some folks to take a look. I would like to get this back to a clean state. cc @hoyosjs @jkoritzinsky @trylek @agocke @tommcdon @JulieLeeMSFT |
…n correctly restore the CoreFX build. It seems that the new CoreFX build isn't on the old blob feeds, so without this fix, we end up restoring the first 5.0.0-alpha.1 build instead of the build we want.
Looks like the packages we're ingesting are not on the old dotnet-core feed. They're only on the 3.1 and 3.1-transport feeds. I've added those feeds to the test build so we can correctly set up Core_Root and the CoreFX test host. |
Thanks @jkoritzinsky. The run has gotten further, but is still failing with missing dependencies. Could not load file or assembly 'System.IO.Pipelines, Version=4.0.2.3, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'. The system cannot find the file specified. Could not load file or assembly 'System.Drawing.Common, Version=4.0.2.2, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'. The system cannot find the file specified. Are there more places that require a package update? |
IIRC those are both out-of-band packages, so it's probably a slightly different fix. I'll continue investigating. |
So it looks like we aren't auto-updating those packages. Additionally, I don't know what feed they're on, so I don't know where to find the right version of those packages or what feeds I need to add. @wtgodbe @Anipik any ideas for where to find the System.Drawing.Common and System.IO.Pipelines packages that include assemblies with matching assembly versions to the ones the CoreFX tests expect here? |
Is an option to disable these tests? This is likely a repeated leg (given this is servicing). |
~ You'd need something like https://github.com/dotnet/coreclr/blob/release/3.1/tests/arm/corefx_linux_test_exclusions.txt, that disables the whole suite. ~ Looks like coreclr/tests/CoreFX/CoreFX.issues.rsp Line 24 in 5ddece2
would do what we need. |
This patch should be enough diff --git a/tests/CoreFX/CoreFX.issues.rsp b/tests/CoreFX/CoreFX.issues.rsp
index 0d1a44452d8..82ca7f8abd7 100644
--- a/tests/CoreFX/CoreFX.issues.rsp
+++ b/tests/CoreFX/CoreFX.issues.rsp
@@ -89,3 +89,10 @@
# Test failure: https://github.com/dotnet/runtime/issues/43166
-nomethod System.IO.Tests.File_GetSetTimes.SetDateTimeMax
+
+# We have issues in restoring the OOB packages to run these tests. Disable for now.
+-nonamespace System.Data.Common.Tests
+-nonamespace System.IO.Pipelines.Tests
+-nonamespace System.Resources.Extensions.Tests
+-nonamespace System.Resources.ResourceManager.Tests
+-nonamespace System.Runtime.Serialization.Formatters.Tests |
Current failure (which looks transitory) Failed to download 'https://dot.net/v1/dotnet-install.ps1'
Unable to download file in 5 attempts. |
I already looped dnceng on that one: dotnet/runtime#55312. It's hitting all our branches. |
thanks @jkoritzinsky and @hoyosjs - what is the next step? I see a few JIT failures and System.Drawing, etc |
The JIT tests are due to a network blip when downloading test assets. The CoreFX tests are just more that we need to add to the exclusion (same issue with OOB System.Drawing.Common). |
@jkoritzinsky looks like the exclusions didn't work at all somehow. I'll download the payload. |
It feels like the issue is more like, the exclusions happen at the reflection level (enumeration happens, the type is in a namespace, sees it and gets excluded). Which means it needs to compile the test before, and in that process we get the loader exception. We have two possible routes here.
|
|
Now that the branch is on servicing, and the churn is low, exclude these as they break far more often than they detect issues. These already run in CoreFX CI on release bits. In case we want to bring them back for checked testing, we need to fix CoreFX.depproj. It has a package - Microsoft.Private.CoreFx.OOB - that's supposed to bring in all deps that are out of box. These are currently not getting restored and this ends up causing File not found issues in the binder when compiling tests, making test exclusions impossible. Please enter the commit message for your changes. Lines starting with '#' will be ignored, and an empty message aborts the commit.
7c84cde
to
a64010f
Compare
The tracing r2r test is failing in several branches cc: @josalem Also, the tracing test on x64 where the
|
@hoyosjs that failure looks a lot like dotnet/runtime#55240 which also happened on R2R arm Linux. I need to look at the dump to be sure, but it's possible this is a regression caused by #28180 since it modified this code path. It is not obvious how or why that would be the case though. The other test failures could also be happening due to this change since they are counter related. I'm not sure why they weren't failing before when we were adding the change though. These tests were passing before and during the PR. Let me investigate it. |
Looking through the code and the dump, it looks like there is an issue on shutdown where a write is happening after an eventsource has been disabled and disposed. The special session for counters has been disabled and Here's my current hunch: there is a pre-existing (pre-#28180) issue with coreclr/src/System.Private.CoreLib/shared/System/Diagnostics/Tracing/EventSource.cs Lines 1350 to 1390 in 09f5b75
This looks to be a race on shutdown path that the old code with the infinite loop issue was hiding. There is an exceedingly small window of time during the The dispose method on EventSource only gets called fully when the I'll continue investigating this to be sure. CC @noahfalk |
Thanks @josalem. Can you create an issue to track the rare race condition? |
Yes, I'll create it when I get back to my desk. |
Completely agreed for servicing purposes. |
* Update branding to 3.1.17 (#28173) * Port from 5.0: Fix Position Independent Code in CMake files (#28143) * CoreCLR PR26323 Port: Fix PIE options * Added missing PIE and RELRO compilation flags. * Merged PR 15832: Port from 5.0: Fix Position Independent Code in CMake files (#28143) Port from 5.0: Fix Position Independent Code in CMake files (#28143) * CoreCLR PR26323 Port: Fix PIE options * Added missing PIE and RELRO compilation flags. * Fix System.Globalization.Native build on Big Sur (#28181) * Fix System.Globalization.Native build on Big Sur * Fix build * Add flags for Linux * [release/3.1] Handle Counter Polling Interval of 0 (#28180) * Backport dotnet/runtime#53836 * Fix test build * update test * update branding to 3.1.18 (#28182) * Update dependencies from https://github.com/dotnet/core-setup build 20210609.1 (#28178) Microsoft.NETCore.App From Version 3.1.9-servicing.20459.3 -> To Version 3.1.17-servicing.21309.1 Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com> * Merged PR 15716: [release/3.1] Use user read+write access for coredump file descriptor open * [release/3.1] #28183 Fix OSX native dependency installation * Avoid upgrading packages that are explicitly installed. * Use a brewfile * Change shebang to use bash and directly execute. * [release/3.1] Update dependencies from dotnet/corefx (#28179) [release/3.1] Update dependencies from dotnet/corefx - Add 3.1 AzDO feeds to the test build to ensure that the test build can correctly restore the CoreFX build. It seems that the new CoreFX build isn't on the old blob feeds, so without this fix, we end up restoring the first 5.0.0-alpha.1 build instead of the build we want. - Exclude tests that depend on OOB assemblies. - Turn off CoreFX test legs in CI. Now that the branch is on servicing, and the churn is low, exclude these as they break far more often than they detect issues. These already run in CoreFX CI on release bits. In case we want to bring them back for checked testing, we need to fix CoreFX.depproj. It has a package - Microsoft.Private.CoreFx.OOB - that's supposed to bring in all deps that are out of box. These are currently not getting restored and this ends up causing File not found issues in the binder when compiling tests, making test exclusions impossible. Please enter the commit message for your changes. Lines starting with '#' will be ignored, and an empty message aborts the commit. Co-authored-by: Jan Jahoda <jajahoda@microsoft.com> Co-authored-by: Ivan Diaz Sanchez <ivdiazsa@microsoft.com> Co-authored-by: Will Godbe <wigodbe@microsoft.com> Co-authored-by: Santiago Fernandez Madero <safern@microsoft.com> Co-authored-by: John Salem <josalem@microsoft.com> Co-authored-by: Anirudh Agnihotry <anirudhagnihotry098@gmail.com> Co-authored-by: dotnet-bot <dotnet-bot@microsoft.com> Co-authored-by: dotnet-maestro[bot] <42748379+dotnet-maestro[bot]@users.noreply.github.com> Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
This pull request updates the following dependencies
From https://github.com/dotnet/corefx