Skip to content

Use a different nuget extraction routine to extract to versioned folders - #4081

Merged
forki merged 4 commits into
fsprojects:masterfrom
baronfel:fix-package-extraction
Sep 13, 2021
Merged

forki merged 4 commits into
fsprojects:masterfrom
baronfel:fix-package-extraction

Conversation

@baronfel

@baronfel baronfel commented Sep 3, 2021

Copy link
Copy Markdown
Contributor

Fixes #4075 by using nuget APIs for extraction to versioned folders directly. I also integrated logging from nuget into our logging, but behind the verboseFn safeguards so as to not spam users.

@baronfel

baronfel commented Sep 3, 2021

Copy link
Copy Markdown
Contributor Author

definitely looks like there's some amount of lock contention happening as a result of this now, based on the test failures.

@baronfel

baronfel commented Sep 3, 2021

Copy link
Copy Markdown
Contributor Author

cool, the only failing test is the same one that's failing in #4080, so if I can figure that out then we should be good to go.

@baronfel

baronfel commented Sep 4, 2021

Copy link
Copy Markdown
Contributor Author

@smoothdeveloper do you have any ideas what might be causing the issue in this test recently?

@smoothdeveloper

Copy link
Copy Markdown
Contributor

@baronfel, no idea

https://github.com/fsprojects/Paket/blob/b2feccc8f9e49f731083d2e2bfc5f47e5328eaa8/integrationtests/Paket.IntegrationTests/FsiExtension.fs

  Error Message:
   file: C:\projects\paket\integrationtests\scenarios\fsi-depmanager\deterministic.output\PaketWithBrokenDepsFile\plot.fsx
command: fsi --langversion:preview --compilertool:C:\projects\paket\integrationtests\Paket.IntegrationTests\..\..\src\FSharp.DependencyManager.Paket\bin\Release\netstandard2.0 C:\projects\paket\integrationtests\scenarios\fsi-depmanager\deterministic.output\PaketWithBrokenDepsFile\plot.fsx
file: C:\projects\paket\integrationtests\scenarios\fsi-depmanager\deterministic.output\PaketWithDepsCanHaveGroups\plot.fsx
command: fsi --langversion:preview --compilertool:C:\projects\paket\integrationtests\Paket.IntegrationTests\..\..\src\FSharp.DependencyManager.Paket\bin\Release\netstandard2.0 C:\projects\paket\integrationtests\scenarios\fsi-depmanager\deterministic.output\PaketWithDepsCanHaveGroups\plot.fsx
file: C:\projects\paket\integrationtests\scenarios\fsi-depmanager\deterministic.output\PaketWithLocalSources\script1.fsx
command: fsi --langversion:preview --compilertool:C:\projects\paket\integrationtests\Paket.IntegrationTests\..\..\src\FSharp.DependencyManager.Paket\bin\Release\netstandard2.0 C:\projects\paket\integrationtests\scenarios\fsi-depmanager\deterministic.output\PaketWithLocalSources\script1.fsx
file: C:\projects\paket\integrationtests\scenarios\fsi-depmanager\deterministic.output\PaketWithRemoteFile\UseGlobbing.fsx
command: fsi --langversion:preview --compilertool:C:\projects\paket\integrationtests\Paket.IntegrationTests\..\..\src\FSharp.DependencyManager.Paket\bin\Release\netstandard2.0 C:\projects\paket\integrationtests\scenarios\fsi-depmanager\deterministic.output\PaketWithRemoteFile\UseGlobbing.fsx
file: C:\projects\paket\integrationtests\scenarios\fsi-depmanager\deterministic.output\SimplePaketTest\fsharp.data.fsx
command: fsi --langversion:preview --compilertool:C:\projects\paket\integrationtests\Paket.IntegrationTests\..\..\src\FSharp.DependencyManager.Paket\bin\Release\netstandard2.0 C:\projects\paket\integrationtests\scenarios\fsi-depmanager\deterministic.output\SimplePaketTest\fsharp.data.fsx
file: C:\projects\paket\integrationtests\scenarios\fsi-depmanager\deterministic.output\SimplePaketTest\plot.fsx
command: fsi --langversion:preview --compilertool:C:\projects\paket\integrationtests\Paket.IntegrationTests\..\..\src\FSharp.DependencyManager.Paket\bin\Release\netstandard2.0 C:\projects\paket\integrationtests\scenarios\fsi-depmanager\deterministic.output\SimplePaketTest\plot.fsx
file: C:\projects\paket\integrationtests\scenarios\fsi-depmanager\deterministic.output\SimplePaketTestTrim\plot.fsx
command: fsi --langversion:preview --compilertool:C:\projects\paket\integrationtests\Paket.IntegrationTests\..\..\src\FSharp.DependencyManager.Paket\bin\Release\netstandard2.0 C:\projects\paket\integrationtests\scenarios\fsi-depmanager\deterministic.output\SimplePaketTestTrim\plot.fsx
file: C:\projects\paket\integrationtests\scenarios\fsi-depmanager\deterministic.output\transitiveloadscripts\b.fsx
command: fsi --langversion:preview --compilertool:C:\projects\paket\integrationtests\Paket.IntegrationTests\..\..\src\FSharp.DependencyManager.Paket\bin\Release\netstandard2.0 C:\projects\paket\integrationtests\scenarios\fsi-depmanager\deterministic.output\transitiveloadscripts\b.fsx
  Standard Output Messages:
 KO: C:\projects\paket\integrationtests\scenarios\fsi-depmanager\deterministic.output\PaketWithBrokenDepsFile\plot.fsx
 KO: C:\projects\paket\integrationtests\scenarios\fsi-depmanager\deterministic.output\PaketWithDepsCanHaveGroups\plot.fsx
 KO: C:\projects\paket\integrationtests\scenarios\fsi-depmanager\deterministic.output\PaketWithLocalSources\script1.fsx
 KO: C:\projects\paket\integrationtests\scenarios\fsi-depmanager\deterministic.output\PaketWithRemoteFile\UseGlobbing.fsx
 KO: C:\projects\paket\integrationtests\scenarios\fsi-depmanager\deterministic.output\SimplePaketTest\fsharp.data.fsx
 KO: C:\projects\paket\integrationtests\scenarios\fsi-depmanager\deterministic.output\SimplePaketTest\plot.fsx
 KO: C:\projects\paket\integrationtests\scenarios\fsi-depmanager\deterministic.output\SimplePaketTestTrim\plot.fsx
 KO: C:\projects\paket\integrationtests\scenarios\fsi-depmanager\deterministic.output\transitiveloadscripts\b.fsx

If you don't mind checking how it behaves locally, if it passes locally, I guess adjusting the print statement to output the expected and actual output will give us an indication on what's wrong on the integration machine.

@forki

forki commented Sep 13, 2021

Copy link
Copy Markdown
Member

what's the status here?

@baronfel

Copy link
Copy Markdown
Contributor Author

Blocked by a failing test in the FSI handler, but this same test is failing in master as well so I'm not sure it's because of these changes.

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.

Paket 6.0.6 does not correctly install packages

3 participants