-
Notifications
You must be signed in to change notification settings - Fork 136
FSharp assemblies are not reported as prebuilts yet get added to the prebuilts tarball #2989
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
Comments
@KevinRansom I tested this offline and none of these F# packages are required to actually build the product. Any idea where I should start looking for why they're being restored? |
These packages are still in the online prebuilts but now with a 7.0 version number, so this wasn't just a 6.0 -> 7.0 transition problem. The offline build also has the F# packages included in the prebuilt tarball but not the prebuilt report. I'm still looking into how exactly this is happening, but we know that we can build offline without the F# packages so it's not a prebuilt leakage. |
Things that I tried:
|
@crummel - Do you have an understanding what causes these to be included in the prebuilt tarball but not reported as prebuilts in the prebuilt report? |
They are still being downloaded but because we have a source-built version the prebuilt report assumes that we will just upgrade it in PVP so they aren't "real" prebuilts - just a circular dependency that will be fixed. The prebuilt tarball logic is simpler and just grabs everything in the NuGet cache that wasn't source-built. |
Confirmed this is still an issue in 8.0 |
Looking at a recent CI build (internal Microsoft link), the following prebuilts are reported:
If you look at the generated
Private.SourceBuilt.Prebuilts.7.0.100.x64.tar.gz
, you will find additional fsharp packages.Investigation should be done to see which is correct (either the report or the generated tarball) and then fix the other.
The text was updated successfully, but these errors were encountered: