Dependabot unknown_error, doesn't create PR #1335
Comments
|
@Ossiam it is difficult to say where the problem lies, I would need to see the full output logs to understand the problem better, if you are comfortable sharing? If not, could you find the part of the log where "MSTest.TestAdapter" starts doing the NuGet update, it will look something like this: There should be some more info below this part of the log to explain why the NuGet update failed. Post back with what you find and we can try dig in to it more. |
|
Thank you for the reply @rhyskoedijk! I'll post a snippet of the logs that relates to MSTest.TestAdapter and the run command What's weird is that MS.TestAdapter is already at version 3.5.2 in master, so I don't understand why it's listed as 3.0.2 in the logs |
|
Following the stack trace, it looks like the error is happening because "no files were changed". As you said, the package is probably already up to date or couldn't be updated due to a NuGet error. Were there any logs between these two lines below? I was expecting to see the logs from native NuGet updater tool appear somewhere which would include the path to the project file it is trying to update and might help identify the file it thinks is out of date and is failing on. |
|
After some investigation, I discovered that the cause of the error with MSTest.TestAdapter and MSTest.TestFramework was that they existed in Directory.Packages.props, but they were not actually in the .csproj. After removing the references the issue was resolved. Now I'm trying to figure out why Dependabot in the second repo only outputs "unknown_error" at the end. |
|
I've resolved the issue. The cause was that the Project Collection Build Service user that Dependabot uses to publish PRs didn't have the correct permissions in the repo. After giving it the correct permissions the issue was resolved. It would have been much easier to diagnose if Dependabot actually specified this in the logs. Is that something that could be investigated/added? |
I hear what you mean, that has been a pretty common problem in the issue history. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Not sure if I should post about this issue here or in dependabot-core. I'm using the dependabot azure extension (useUpdateScriptvNext, image 1.34) to run dependabot on multiple C# repos. For my main repo, some packages fail to update but still creates a PR:
But for my second repo, I get the error posted below, which causes it to not create a PR. Is there a flag I can use to print the full logs so I can pinpoint the issue?
After googling about the issue, some people suggested to add the nuget-feed as a registry, but that didn't resolve it.
On the dependabot-core github, some people have posted about similar issues, and that it's "resolved"
dependabot/dependabot-core#8992
Directory.packages.props for the project I'm trying to update:
The text was updated successfully, but these errors were encountered: