DIAGNOSTIC (do not merge): assembly bind logging for net472 importer tests - #728
Closed
wasabii wants to merge 1 commit into
Closed
DIAGNOSTIC (do not merge): assembly bind logging for net472 importer tests#728wasabii wants to merge 1 commit into
wasabii wants to merge 1 commit into
Conversation
Not for merge. IKVM.Tools.Importer.Tests on net472 fails every row with Could not load 'System.Collections.Immutable, Version=10.0.0.0' ---> Could not load 'System.Collections.Immutable, Version=8.0.0.0' at IKVM.Tools.Importer.ImportOptions..ctor() The generated app.config redirects 0.0.0.0-8.0.0.0 to 8.0.0.0, so a 10.0.0.0 reference falls outside the range and never gets redirected. The file on disk really is 8.0.0.0, so the bind fails outright. Nothing in the test output explains the 10.0.0.0 reference. All 68 assemblies beside the test top out at 8.0.0.0, IKVM.Runtime and IKVM.Java don't reference it at all, and the SDK's test platform assemblies don't either. The CI log notes that bind logging is off, so turn it on for this job and print any failure log mentioning the assembly. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Draft, not for merge. Temporary instrumentation to identify one unknown, then revert.
Why
IKVM.Tools.Importer.Testson net472 fails every row onmainwith:The generated
IKVM.Tools.Importer.Tests.exe.configcontains:A 10.0.0.0 reference falls outside
0.0.0.0-8.0.0.0, so the redirect never applies and the loader binds 10.0.0.0 literally against a file that really is 8.0.0.0 (FileVersion 8.0.23.53103). That much is confirmed from the run 29223646609 artifact.The unknown
Nothing I can enumerate explains where the 10.0.0.0 reference comes from. Checked and ruled out:
tests/IKVM.Tools.Importer.Tests/net472/— highest is 8.0.0.0 (IKVM.CoreLib,IKVM.Tools.Importer,System.Reflection.Metadata); the rest ask for 1.2.3.0–6.0.0.0IKVM.Runtime.dll/IKVM.Java.dll— no reference to it at allThe failing run logs
WRN: Assembly binding logging is turned OFF., so this turns it on and prints any bind-failure log naming the assembly. That names the requester directly instead of guessing.Changes
Two steps in the
testjob, both gated to Windows +IKVM.Tools.Importer.Tests:HKLM\SOFTWARE\Microsoft\FusionLogFailures/EnableLogwith aLogPathunder the work dirif: always(), strips HTML and prints matching failure logs to the job outputOnce the requester is known, this is reverted and the real fix goes in separately.
Related: this is one of the failures blocking #725, whose own change is correct and adds no failures of its own.