[master] Updating CoreFx, CoreClr, Standard to beta-25118-01, beta-25117-08, beta-25117-02 respectively

[dotnet-bot]

/cc @dotnet/core-setup-contrib

[gkhanna79]

The PR is failing with the following:

Discovered: PortableTestApp System.MethodAccessException: Attempt by method 'System.Threading.ReaderWriterLockSlim.TryEnterWriteLockCore(TimeoutTracker)' to access method 'System.Environment.get_CurrentManagedThreadId()' failed.

@stephentoub @karelz @danmosemsft Is this a known issue in CoreFX?

[karelz]

It's not a known problem - it seems to be introduced by this new CoreCLR version.
https://github.com/dotnet/corefx/issues?q=is%3Aissue+MethodAccessException+is%3Aclosed

[gkhanna79]

None of those issues are like the ones you listed (which seem to be different issues resulting in similar exception). It will be good to have someone take a look at what changed in this version of corefx being brought in.

[karelz]

Ah, sorry. I didn't realize this is core-setup repo and not CoreFX repo with CoreCLR insertion failing.
@stephentoub @mellinoe can you please take a look?

[stephentoub]

Environment in CoreCLR was made internal here:
dotnet/coreclr@14207f4#diff-a86acb0812ee80bbed4ae851c5e8c65cR42
There were CoreFx fixes made to adapt to it here:
dotnet/corefx#17269
Presumably it's related to this.
cc: @rahku

[rahku]

@stephentoub is correct. Next corefx update should have the fix

[gkhanna79]

@karelz have there been no CoreFX builds over the weekends? I dont see a PR with updated CoreFX that would contain the fix.

[gkhanna79]

Closing against #1782 that has the same issue.

[karelz]

@gkhanna79 I don't know how pipeline builds work - @weshaggard?
Naively I would expect that there are continuous builds of CoreFX. At least I don't see any reason/sign why there wouldn't be - new PRs are getting through on GitHub.

cc @danmosemsft

[weshaggard]

We don't have continuous builds for CoreFX we have daily triggers at 6am and 6pm every weekday.

#1784 has the updated corefx build from today.