Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Revert changes for "ResultsCache ignores some of the BuildRequest dat… #9718

Conversation

YuliiaKovalova
Copy link
Member

Context

The changes #9565 seem to cause regression Bug 1943607 in Azure dev ops.
Revert changes to unblock the customers and get back to it later.

Copy link
Member

@ladipro ladipro left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you!

src/Build/BackEnd/Shared/BuildResult.cs Show resolved Hide resolved
@YuliiaKovalova YuliiaKovalova merged commit 553649b into dotnet:main Feb 8, 2024
8 checks passed
@dfederm
Copy link
Contributor

dfederm commented Mar 11, 2024

FYI, this also seemed to be causing some issues when using differing versions of MSBuild:

MSBUILD : error : MSB4256: Reading input result cache files from path "..." encountered an error: Unable to read beyond the end of the stream.
MSBUILD : error : MSB4258: Writing output result cache file in path "..." encountered an error: Object reference not set to an instance of an object.

Currently this repros when importing results in 17.10 from a file produced with 17.9.

The issue does not repro when the consuming (2nd) build is using IntPreview (nor GA), so I'm guessing this revert mitigates the issue.

I didn't look too deeply, but my guess is that the problem is that a field was added to BuildResult, which is causing the serialization issues.

ladipro added a commit to ladipro/msbuild that referenced this pull request Apr 10, 2024
ladipro added a commit to ladipro/msbuild that referenced this pull request Apr 10, 2024
ladipro added a commit that referenced this pull request Apr 15, 2024
ladipro added a commit that referenced this pull request Apr 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants