-
Notifications
You must be signed in to change notification settings - Fork 4.9k
Update BuildTools, CoreClr, CoreFx, CoreSetup, ProjectNTfs, ProjectNTfsTestILC to prerelease-02312-02, preview1-26013-03, preview1-26013-06, preview1-26012-06, beta-26013-00, beta-26013-00, respectively (master) #25872
Update BuildTools, CoreClr, CoreFx, CoreSetup, ProjectNTfs, ProjectNTfsTestILC to prerelease-02312-02, preview1-26013-03, preview1-26013-06, preview1-26012-06, beta-26013-00, beta-26013-00, respectively (master) #25872
Conversation
@ahsonkhan any idea when this would go in? We are blocked on fix for https://github.com/dotnet/coreclr/issues/15432 |
35f7112 (9:x: 4:heavy_check_mark:) Update BuildTools, CoreClr, CoreFx, CoreSetup, ProjectNTfs, ProjectNTfsTestILC to prerelease-02312-02, preview1-26011-03, preview1-26012-03, preview1-26012-06, beta-26012-00, beta-26012-00, respectively |
35f7112
to
51ead33
Compare
See previous update which got blocked on some other test failures - @swgillespie, any progress on the issue that resulted in System.Net.Sockets tests to fail? |
@ahsonkhan I have been looking at this issue but I have still been unable to find the root cause. Should I revert the PR to unblock this? @pakrym Reverting that PR will also fix your issue, since it's the same PR that introduced the bug in the first place. |
How long do you expect it would take? Imo, I would revert the PR to unblock this if you won't be able to resolve it by eod, especially since I also have dependencies upcoming that would require clean updates from coreclr/ProjectN. |
@ahsonkhan In that case I will revert it. I still don't understand the root cause and I don't have a ETA. |
Great. Tyvm. Please cc me on your PR so I know when to expect an update of coreclr (and then I can cherry-pick my changes from #25770). |
Might be easiest; coreclr and corefx are currently out of sync due to the api change
So its currently hard to test them together. When they are back in sync then you can run the tests:
in coreclr which should help track down the bug and/or determine if its fixed? |
@benaadams great, thanks! i'm not used to GC issues leaking into corefx... unfortunately the PR in question here touches async pinned handles and I guess the CoreCLR test suite doesn't do much I/O. |
They are good verifying tests as they pull in current corefx and run with the PRs coreclr; for example I'm using them to verify changes to Dictionary dotnet/coreclr#15460 (comment) as its a bit far ranging to just do the Collection tests locally from corefx on my single platform |
51ead33 (10:x: 4:heavy_check_mark:) Update BuildTools, CoreClr, CoreFx, CoreSetup, ProjectNTfs, ProjectNTfsTestILC to prerelease-02312-02, preview1-26013-01, preview1-26012-03, preview1-26012-06, beta-26012-00, beta-26012-00, respectively |
51ead33
to
20b833d
Compare
20b833d (10:x: 4:heavy_check_mark:) Update BuildTools, CoreClr, CoreFx, CoreSetup, ProjectNTfs, ProjectNTfsTestILC to prerelease-02312-02, preview1-26013-01, preview1-26013-03, preview1-26012-06, beta-26012-00, beta-26012-00, respectively |
20b833d
to
1f19144
Compare
1f19144 (1:x: 10:hourglass: 3:heavy_check_mark:) Update BuildTools, CoreClr, CoreFx, CoreSetup, ProjectNTfs, ProjectNTfsTestILC to prerelease-02312-02, preview1-26013-01, preview1-26013-04, preview1-26012-06, beta-26013-00, beta-26013-00, respectively |
1f19144
to
e5bdd62
Compare
e5bdd62 (3:x: 8:hourglass: 3:heavy_check_mark:) Update BuildTools, CoreClr, CoreFx, CoreSetup, ProjectNTfs, ProjectNTfsTestILC to prerelease-02312-02, preview1-26013-01, preview1-26013-04, preview1-26012-06, beta-26013-00, beta-26013-00, respectively |
e5bdd62
to
3378c4e
Compare
3378c4e (10:x: 4:heavy_check_mark:) Update BuildTools, CoreClr, CoreFx, CoreSetup, ProjectNTfs, ProjectNTfsTestILC to prerelease-02312-02, preview1-26013-02, preview1-26013-04, preview1-26012-06, beta-26013-00, beta-26013-00, respectively |
3378c4e
to
5543f18
Compare
5543f18 (10:x: 4:heavy_check_mark:) Update BuildTools, CoreClr, CoreFx, CoreSetup, ProjectNTfs, ProjectNTfsTestILC to prerelease-02312-02, preview1-26013-03, preview1-26013-04, preview1-26012-06, beta-26013-00, beta-26013-00, respectively |
5543f18
to
fd0ff4d
Compare
fd0ff4d (10:x: 4:heavy_check_mark:) Update BuildTools, CoreClr, CoreFx, CoreSetup, ProjectNTfs, ProjectNTfsTestILC to prerelease-02312-02, preview1-26013-03, preview1-26013-05, preview1-26012-06, beta-26013-00, beta-26013-00, respectively |
…fsTestILC to prerelease-02312-02, preview1-26013-03, preview1-26013-06, preview1-26012-06, beta-26013-00, beta-26013-00, respectively
fd0ff4d
to
c73acae
Compare
The ApiCompat error is currently blocking the ProdCon build. Is there a plan to resolve this issue? |
Cherry-picked the commits from #25770 |
System.Net.Sockets.Tests and System.Net.Http.Functional.Tests failing; look like same errors as before? #25821 (comment)
|
Couldn't update this pull request: Head commit author 'ahsonkhan' is not 'dotnet-maestro-bot' |
cc @swgillespie, @jkotas, any ideas? |
@dotnet-bot test Linux x64 Release Build |
Looks like preview1-26013-03 version of coreclr doesn't contain @swgillespie's revert change dotnet/coreclr#15498. So there must be something else causing these failures. |
Couldn't update this pull request: Head commit author 'ahsonkhan' is not 'dotnet-maestro-bot' |
Couldn't update this pull request: Head commit author 'ahsonkhan' is not 'dotnet-maestro-bot' |
Closing this PR so a new one can get generated. We still have Windows specific test failures. |
@ahsonkhan The Windows specific socket failures are caused by your Pin() changes. I am going to revert the change in CoreCLR to get things unstuck. |
This change - dotnet/coreclr#15410? |
No description provided.