Update CoreClr, CoreFx, CoreSetup, External, ProjectNTfs, ProjectNTfsTestILC, Standard to preview2-25631-03, preview2-25631-02, preview2-25631-01, beta-25627-00, beta-25630-04, beta-25630-04, preview1-25631-01, respectively (master)#23563
Conversation
1a25146 to
f5d318c
Compare
f5d318c to
20b71b4
Compare
20b71b4 to
23d3324
Compare
23d3324 to
c32c2c9
Compare
c32c2c9 to
7a4a948
Compare
|
@dotnet-bot test OSX x64 Debug Build please (https://github.com/dotnet/corefx/issues/23585, https://github.com/dotnet/corefx/issues/23586) |
a8e7157 to
c2cf314
Compare
|
OSX failures: |
|
Win 10 x64 failures (note missing line numbers) |
|
Win10 Nano failure (maybe just flaky) @krwq any thoughts about the XPath failure above? |
|
@ViktorHofer @mellinoe any thoughts about the BigInteger failures above? Uh, I see @stephentoub opened issues for both, does that mean they repro without the new CLR? |
No, I opened those issues in response to this PR. But as this PR is about updating to a new coreclr, if tests in the repro are failing with this PR, that means either checked in tests are wrong or checked in coreclr code is wrong. |
c2cf314 to
55d3105
Compare
55d3105 to
fd1951b
Compare
fd1951b to
8dfc79a
Compare
8dfc79a to
0c24f07
Compare
|
https://github.com/dotnet/corefx/issues/23585 suggests a GC hole. Perhaps the xpath one is also a GC hole symptom. @swgillespie @jkotas what is the best way to narrow down a GC hole? I will try see if I can repro locally. |
a685d3e to
af7f1c5
Compare
af7f1c5 to
3fa9777
Compare
|
Still waiting for a coreclr newer than |
3fa9777 to
df26c8f
Compare
df26c8f to
a6ab76d
Compare
|
build succeeded, hopefully it will kick this shortly |
a6ab76d to
29f8c3b
Compare
|
@mmitche did you get to add the logging? |
|
@ahsonkhan @adriangodong is my build break fix correct? e360b05 |
|
@danmosemsft That isn't an error at that point since not all processes are killed at that exact point (see message below that). However i would have expected that VCBSCompiler was the culrpit, and apparently not. If you see this at the beginning of a job, that is a real issue. |
…TestILC, Standard to preview2-25631-03, preview2-25631-02, preview2-25631-01, beta-25627-00, beta-25630-04, beta-25630-04, preview1-25631-01, respectively
e360b05 to
f4b098d
Compare
S.R.WindowsRuntime is a friend with CoreLib. HResults definition in CoreLib has changed and it is colliding local HResults definition in S.R.WindowsRuntime now.
|
Build is now broken due to dotnet/coreclr#13611. Fixing in dotnet/coreclr#13727. |
|
I have just pushed a fix here that does not require waiting for new CoreCLR build. |
|
Thanks. Shall I close dotnet/coreclr#13727 then? |
|
I think so. The fewer places where S.R.WindowsRuntime depends on friend access to CoreLib the better. |
|
I agree. |
…-UpdateDependencies Update CoreClr, CoreFx, CoreSetup, External, ProjectNTfs, ProjectNTfsTestILC, Standard to preview2-25631-03, preview2-25631-02, preview2-25631-01, beta-25627-00, beta-25630-04, beta-25630-04, preview1-25631-01, respectively (master) Commit migrated from dotnet/corefx@a1050c9
No description provided.