Uh oh!
There was an error while loading. Please reload this page.
Src gen: use GetBestTypeByMetadataName instead of GetTypeByMetadataName - #59092
Conversation
ghost
commented
Sep 14, 2021
Tagging subscribers to this area: @eiriktsarpalis, @layomia Issue DetailsChange remaining source generator locations that use See #57349 This is a simple 1:1 method replacement; has been previously tested in System.Text.Json (which has a unit test) and by Roslyn. This may be ported to 6.0.
|
6e95673 to
2f8b5cdCompareUh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
db8fb31 to
129b716CompareWASM issue likely caused by #51961 binlog section (crash on console log: |
lewing
commented
Sep 20, 2021
cc @vargaz |
lewing
commented
Sep 20, 2021
Something is killing the processes here, we need to figure out what and why before we can work on solving it. |
c06550c to
4dda364Comparesteveharter
commented
Sep 21, 2021
lewing
commented
Sep 21, 2021
@steveharter have you checked against main after #59352 landed? |
There was a problem hiding this comment.
you shouldn't need a new group for this, the exclusions 4 lines above should be enough but it looks like the paths are incorrect? I see
./Microsoft.Extensions.Logging.Abstractions/tests/Microsoft.Extensions.Logging.Generators.Tests/Microsoft.Extensions.Logging.Generators.Roslyn4.0.Tests.csproj
./Microsoft.Extensions.Logging.Abstractions/tests/Microsoft.Extensions.Logging.Generators.Tests/Microsoft.Extensions.Logging.Generators.Roslyn3.11.Tests.csproj
There was a problem hiding this comment.
There was a problem hiding this comment.
shouldn't the path start with Microsoft.Extensions.Logging.Abstractions\tests not Microsoft.Extensions.Logging\tests ?
There was a problem hiding this comment.
since it's pointing at the wrong path and passing those old exclusions can probably be removed. I'll do it in a separate pr
f6cf633 to
e08eb3dComparesteveharter
commented
Sep 21, 2021
I just did a rebase and the same crash is occuring. |
Uh oh!
There was an error while loading. Please reload this page.
57b2ae9 to
8cf4af3Compare8cf4af3 to
9b20c61Compare32c3b4b to
8e2ca47Compareericstj
commented
Sep 28, 2021
Looks like test failure is in regex source generator on checked coreclr. May not be related to this change, see #10680. cc @stephentoub |
ericstj
commented
Sep 28, 2021
I see @stephentoub disabled that test here: 5d71e32 |
stephentoub
commented
Sep 28, 2021
Yeah, the actual issue is the test is attributed with a SkipOnCoreClr attribute in order to avoid running on checked runtimes but the test isn't being skipped, as the attribute is being processed in a way different from what was expected. I disabled it while the attribute gets fixed. |
@stephentoub while you're here, this PR might be relevant for your RegEx source generator: edit, looks like I should expand my search by a couple lines. |
ericstj
commented
Sep 29, 2021
/azp run runtime |
|
Azure Pipelines successfully started running 1 pipeline(s). |
steveharter
commented
Sep 29, 2021
Build failure in |
steveharter
commented
Sep 29, 2021
/backport to release/6.0 |
Started backporting to release/6.0: https://github.com/dotnet/runtime/actions/runs/1288124568 |
@steveharter backporting to release/6.0 failed, the patch most likely resulted in conflicts: $ git am --3way --ignore-whitespace --keep-non-patch changes.patch
Applying: Use GetBestTypeByMetadataName instead of GetTypeByMetadataName
Using index info to reconstruct a base tree...
M src/libraries/Microsoft.Extensions.Logging.Abstractions/gen/LoggerMessageGenerator.Parser.cs
Falling back to patching base and 3-way merge...
Auto-merging src/libraries/Microsoft.Extensions.Logging.Abstractions/gen/LoggerMessageGenerator.Parser.cs
CONFLICT (content): Merge conflict in src/libraries/Microsoft.Extensions.Logging.Abstractions/gen/LoggerMessageGenerator.Parser.cs
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Use GetBestTypeByMetadataName instead of GetTypeByMetadataName
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
Error: The process '/usr/bin/git' failed with exit code 128Please backport manually! |
Change remaining source generator locations that use
Compilation.GetTypeByMetadataNameto an extension that addresses conflict cases. The guidance and extension implementation is from the Roslyn team.See #57349
This is a simple 1:1 method replacement; has been previously tested in System.Text.Json (which has a unit test) and by Roslyn.
This may be ported to 6.0.