Following commit skipped the functional test as this was blocking the mirror and is potentially a behavior change to which we need to react.
Reference files(Note: Rename the file extensions to .html):
NewErrorPage.zip
OldErrorPage.zip
cc @pranavkm @mikeharder
Commit: 106b34867d7b7bba45e36ea4385e68311cad3b13
08965550addf660ad1ec43d32c93987eb205192e
馃憤
It appears this issue is resurfacing again in the mirror, probably because the corefx team merged their commits from preview1(where it regressed) to dev(where it was working when @NTaylorMullen unskipped this).
@kichalla - should this issue be in preview2 then?
Yes, this would be for preview2. Changed the milestone now. I re-opened this issue: https://github.com/aspnet/Diagnostics/issues/372
Commit to revert later: d916cfeaddbda9f17da1998e42af85ec8c8dc3f4
@kichalla Do the right people know that this was regressed over on the coreclr team?
@NTaylorMullen I created the following issue now: https://github.com/dotnet/corefx/issues/19838
This has been fixed. Reverted change 3c7a2dc847b4c4fa8d0d83bc0bcb5308f2b8bca4
Re-skipping for desktop applications. https://github.com/dotnet/corefx/issues/19838
Working around this by adding:
<DebugType Condition="'$(TargetFrameworkIdentifier)'=='.NETFramework'">Full</DebugType>