-
Notifications
You must be signed in to change notification settings - Fork 4.9k
Update CoreClr, CoreFx, CoreSetup, ProjectNTfs, ProjectNTfsTestILC, Standard to preview2-25708-01, preview2-25707-02, preview2-25707-02, beta-25708-00, beta-25708-00, preview1-25707-01, respectively (master) #23784
Update CoreClr, CoreFx, CoreSetup, ProjectNTfs, ProjectNTfsTestILC, Standard to preview2-25708-01, preview2-25707-02, preview2-25707-02, beta-25708-00, beta-25708-00, preview1-25707-01, respectively (master) #23784
Conversation
f18be4e to
d4125d1
Compare
|
@mikem8361, this is related to the issue I mentioned to you over email... the latest coreclr is failing some stack trace tests: Is this behavior change by design? If it is, the tests will need to be fixed before / as part of this PR to bring in the latest runtime. EDIT: I just noticed these failures are actually in the netfx build. Hmmm.... |
|
@kouvel, the threading tests all appear to be hanging... could this be related to your latest changes related to spinning or other things in coreclr? |
|
Taking a look |
d4125d1 to
0fb1caa
Compare
|
Yes the hangs in threading/concurrent tests are caused by my change, sorry about that. PR dotnet/coreclr#13766 fixes the hangs. |
|
dotnet/coreclr#13766 is merged now and the hangs should be fixed once a CoreCLR that includes the change is published |
|
Thanks, @kouvel. |
0fb1caa to
4ea8617
Compare
4ea8617 to
cfb214a
Compare
|
@dotnet-bot test Linux x64 Release Build please (seg faults on CentOS) |
cfb214a to
8040da0
Compare
8040da0 to
ea5c91c
Compare
ea5c91c to
f12ae27
Compare
|
OSX segfault in System.Security.Cryptography.X509Certificates @bartonjs there is a dumpfile for this but I don't know whether you have been successful with Mac dumps from dumpling. It may need trying locally (or this could be sporadic/unrelated) |
|
RedHat.73 segfault in |
@danmosemsft I've not investigated any segfaults (that I can remember) since dumpling was working. Are there directions? |
|
@bartonjs well, it turns out it's not working on OSX. Looking up the guid from the log, I get http://dumpling.azurewebsites.net/api/dumplings/archived/36af96fc271dcaa04b5c25fd53d13eeee63c6d54 which is empty... |
f12ae27 to
7dc993b
Compare
7dc993b to
00110e3
Compare
00110e3 to
6ad15af
Compare
6ad15af to
f58980b
Compare
3ffaab9 to
7a5765b
Compare
|
@dotnet-bot test this please |
|
@dotnet-bot test Linux x64 Release Build please (a bunch of seg faults) |
|
(@danmosemsft, the seg faults were in the same suites on some of the same distros you mentioned) |
|
It failed the same two suites again with seg faults on the same OSes: RedHat, CentOS, and Fedora. @danmosemsft, worth having someone take a look? |
7a5765b to
a6004fa
Compare
…tandard to preview2-25708-01, preview2-25707-02, preview2-25707-02, beta-25708-00, beta-25708-00, preview1-25707-01, respectively
a6004fa to
d9bfacd
Compare
|
This time it was a nuget issue, and a seg fault in drawing (as seen elsewhere) Let's see if we can narrow down tests/distro .. unfortunately the force pushes cause the run data to get blown away each time. @dotnet-bot test this please |
|
Based on https://github.com/dotnet/coreclr/issues/13779, the seg faults may be due to my change as well :(, I'm fixing |
…tandard to preview2-25708-01, preview2-25707-02, preview2-25707-02, beta-25708-00, beta-25708-00, preview1-25707-01, respectively (dotnet/corefx#23784) Commit migrated from dotnet/corefx@0237599
No description provided.