-
Notifications
You must be signed in to change notification settings - Fork 521
Use a different nuget extraction routine to extract to versioned folders #4081
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
Conversation
|
definitely looks like there's some amount of lock contention happening as a result of this now, based on the test failures. |
|
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. |
|
@smoothdeveloper do you have any ideas what might be causing the issue in this test recently? |
|
@baronfel, no idea 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. |
|
what's the status here? |
|
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. |
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.