-
-
Notifications
You must be signed in to change notification settings - Fork 66
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
Yarn Berry Errors with record_update_job_error
; Equivalent Project Runs Well on Github
#1518
Comments
{"message":"Error while loading \".yarnrc.yml\"."}},"type":"record_update_job_error"}
; Equivalent Project Does Not Fail on GIthubrecord_update_job_error
; Equivalent Project Does Not Fail on GIthub
record_update_job_error
; Equivalent Project Does Not Fail on GIthubrecord_update_job_error
; Equivalent Project Runs Well on GIthub
@epicstar thanks for the reproduction repo; I will attempt to reproduce this in DevOps and see what is going on. |
record_update_job_error
; Equivalent Project Runs Well on GIthubrecord_update_job_error
; Equivalent Project Runs Well on Github
@rhyskoedijk Here's a link to the logs. The logs are so big I had to give you the files through OneDrive :( Still not sure why the yarnrc yaml can't be read. My initial uneducated hunch is that it is accidentally being ignored by the docker container. |
I tested on Github vs. DevOps as well and am seeing the same behavior. Mine finishes in about 4 minutes on github but times out on DevOps. |
Describe the bug
As of 3 weeks ago, every update using V2 of the Dependabot pipeline runner in Azure Devops gives us this error in our yarn v4 monorepo code:
For a more detailed sample snippet:
If running this project with the exact code in Github, the code runs successfully.
Categorization
Repository
https://github.com/epicstar/dependabot-yarn-test/
I have given you the repo in Github to prove it works fine on Github.
However, because our organization is private, I cannot give you the Azure Devops version of the code. Rest assured, the code is the exact same minus blanking out the
githubConnection
property in the Azure Devops pipeline.To Reproduce
Steps to reproduce the behavior:
Please see README of https://github.com/epicstar/dependabot-yarn-test to run in Azure Devops.
You will have to push this repo there. The Azure Pipeline YAML should be in the given repository.
Expected behavior
It should be like the Github repo outputs:
Logs and screenshots
In Azure:
Extension (please complete the following information):
Server (please complete the following information):
Logs TBD SOON
Additional context
We spotted this problem in our original repo that was occurring on our private Azure Artifacts version of NPM Registry; however, the problem is also happening on the standard public NPM Registry.
We had to move to V2 from V1 because we had problems with running the pipeline extension with our Private Azure Artifacts (upstream).
In addition, #1441 is not an issue on Dependabot as Dependabot on Github runs this repo in 16 minutes, as opposed to 1 hour 10 minutes.
The text was updated successfully, but these errors were encountered: