-
Notifications
You must be signed in to change notification settings - Fork 132
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
VerifyVersionFile
test fails in bootstrapping stage 2 build
#3426
Comments
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
I wonder if this was a side effect of dotnet/installer#16161? |
I don't think that's relevant since that PR had changes to the version computation, not the commit SHA. I was initially suspecting Premek's source link changes but I'm not sure that's the cause either. It's really baffling. The binlog shows that |
As a sanity check, I ran a build that outputs the value of |
I tested re-enabling this and it shows up in the initial build, not just the stage 2 build. To me, that means a change occurred in Arcade or SDK that caused the regression. Initially that only showed up in stage 2 build, but now that the new versions of those things are being used for stage 1, it reveals the same test failure. |
This is caused by source-link being bundled with the SDK in dotnet/sdk#31632. Because of that |
It fails on this line because the
.version
file that's created only has one line in it. It doesn't contain the repo commit but does have the version. The MSBuild property that's used to input the repo commit is$(RepositoryCommit)
. Looking at the binlog shows that this property is not set for thepackage-source-build
project. This is a regression because I see that it was set in the stage 2 build in the past.The text was updated successfully, but these errors were encountered: