Update CoreSetup to preview1-25719-04 (master) - #7606
Conversation
|
/cc @ahsonkhan |
|
FYI - @dotnet/dotnet-cli |
|
@eerhardt, awesome. Tyvm for the update! |
|
@KevinRansom the failing tests are all F#, can you take a first look at this? |
5f395b1 to
f6cabc8
Compare
|
@livarcocc @eerhardt on it. |
f6cabc8 to
1a29c17
Compare
1a29c17 to
0c3d356
Compare
0c3d356 to
55df479
Compare
55df479 to
fd03e1b
Compare
fd03e1b to
5da64ee
Compare
5da64ee to
1e63e8f
Compare
1e63e8f to
5b147d1
Compare
|
@KevinRansom - any update? |
5b147d1 to
a44abef
Compare
a44abef to
872bff2
Compare
|
@eerhardt, @KevinRansom, any eta on this update? |
|
I've tried to do the binary search and the problem came in between: But it doesn't change anything in my and @briansull's lists on the gist, since as you can see, the 2.1.0-preview2-25625-01 and the previously known last good 2.1.0-preview2-25616-02 were both built from the same commit. |
|
Using Here is the working disassembly from the previous build: |
|
Adding @dsyme |
872bff2 to
e2ae0bd
Compare
e2ae0bd to
757bd7f
Compare
757bd7f to
550b42a
Compare
|
PR for JIT fix into CoreCLR is up at dotnet/coreclr#13957. |
550b42a to
a0e0c0c
Compare
|
Does |
|
No it doesn't. So the next build of core-setup should have the fix. |
|
All Unix builds are segfaulting in crossgen with the latest coresetup version. I've reproed it locally and it seems to be a codegen issue - see https://github.com/dotnet/coreclr/issues/13942 |
a0e0c0c to
7d8adb6
Compare
7d8adb6 to
51a9a2a
Compare
|
Official builds have been broken for all |
|
But once the official builds are unblocked, I believed that last remaining blocking fix is in core-setup. |
51a9a2a to
7287790
Compare
Builds are unblocked & CI is green. Can we merge the PR? |
/cc @dotnet/dotnet-cli