-
Notifications
You must be signed in to change notification settings - Fork 258
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
NuGet.targets(498,5): error : Could not find a part of the path '/tmp/NuGetScratch #7341
Comments
@joshfree: Did this error occur on a DevOps Pipelines
The agent should be using .NET Core SDK 2.1.403: |
I'm not sure the details on the infra -- @MattGal should know |
Speak of the me and I shall appear. Looking. |
@mikeharder to answer your question, this specific job runs on a Jenkins agent whose VHD was made by @mmitche a bit over a year ago: (ubuntu1604-20170925-1) . I'm looking at the errors too to see if I can provide more useful data. |
@joshfree I can't find any other failures on this build def that both still have their logs available and have this problem. However, one possible cause if we ever get onto such a machine is that tmp can be over-filled on Linux and OSX machines, making further file operations within the /tmp folder fail. It seems very unlikely for the hosted agents though since they are reset every build. |
@MattGal: Thanks. It seems more likely this is a general issue with NuGet on Linux, rather than specific to one type of agent. |
@mikeharder I agree and your data definitely makes it seem that way, I was just listing an issue with tmp folders I'd seen. |
@MattGal @joshfree @mikeharder Hello, we can see the same issue on I've seen it occur only on the macOS agent so far. |
Have same error in Azure DevOps, sometimes it works and sometimes the error is thrown:
|
Im also seeing this issue:
We are building a .net core project on the Azure Devops hosted Ubuntu image. Generally if you re-trigger the build the problem goes away for a bit, but this is not ideal in a ci environment |
We are also seeing the same issue. And as @MarkDordoy said re-triggering the build it works, but it's breaking all our CI environment.
|
Is it also reproducible on dev box instead if Azure DevOps? and Can someone provide me verbose logs for the issue? |
Could any of you that can reproduce the issue often enough try redirecting TMPDIR to a user-local folder before running restore, and report back to us whether you still see the problem. |
@nkolev92 I can confirm that that works for me. ( |
Thanks @aveao |
I use the aur package "nuget-stable" and use msbuild to build mono stuff. So… I assume that's what it is. |
I have a fix for nuget.exe under mono that could be causing this issues in NuGet/NuGet.Client#2691. |
Issue occurs periodically. Run build again solves issue. Using "Hosted Ubuntu 1604" agent. |
@stas-lucky Have you ever used nuget.exe on mono on the machine where the problems happen? |
I am seeing this issue on our builds of Azure PowerShell on both the public hosted Linux and macOS workers in ADO. It seems to happen randomly.
|
Same issue. Seems to be random, usually works when I rerun it. Using Azure Devops as well. |
@nkolev92 fixed it for Mono in 5.0. Couldn't find anything involving dotnet.exe code paths. |
@joseccruz I'm digging into some potentially related code on the side, but it's hard to predict whether that's truly the problem without more information or a repro. |
+1 on this, happens intermittently for us on CI builds on Ubuntu. |
Just ran into this again. It's been happening for a long time now. Same issue as everyone else: Ubuntu 16.04 Microsoft-hosted build agent.
|
+1 here |
looks like is are the only ones not using their hosted agents ;) pretty smart, eh? xD |
Update I have another fix in the related code path in NuGet/NuGet.Client#2795. I will update again whenever this fix makes it in the previews of (2.1.700, 2.2.300 & 3.0.100). |
I've just started playing around with ADO hosted agents and I hit this pretty quickly. I don't want to tie up one of my agents we're paying for but I imagine if I just ran the same build on a schedule every 10 minutes with some jitter it would fail several times a day. I encountered it on the 10th build or so. |
The fix will be in If/When you upgrade to these versions, let me know if you still see issues. |
I'm also seeing this intermittently on Azure Devops. @nkolev92 are those version numbers of .NET Core? If so, how do I set which version to use with that precision? I'm only aware of how to choose the major and minor version, using the csproj file ( |
That's the .NET Core SDK version. It's what allows you to build the application. It's something you need to update on the specific machines (Azure Pipelines has an install task + you can use global.json to pin the SDK version). Hope the following resources help. https://docs.microsoft.com/en-us/dotnet/core/sdk |
Has anyone seen issues with: 2.1.700 Thanks! |
At this point, I am closing this issue as fixed. |
When will azure pipelines use 2.2.300 or higher be default? I don't really want to pin a specific sdk version in all of my repositories |
got the same (similar?) error with monodevelop |
Why was the issue closed. Pls reopen it. This issue is faced constantly in our ado. |
We're occasionally seeing a spurious failure mentioning the
/tmp/NuGetScratch
path on Ubuntu 16.04 in CI on latest .NET Core 3.0 (master) builds:dotnetcli/sdk/3.0.100-alpha1-009626/NuGet.targets(498,5): error : Could not find a part of the path '/tmp/NuGetScratch/527e64f2-3196-46c8-b4c2-0a6353faf093'.
link to corefx-lab
I'll update this issue with additional links if/when we see more hits
The text was updated successfully, but these errors were encountered: