-
-
Notifications
You must be signed in to change notification settings - Fork 25.8k
DOC Add lock-file trick to help debug CI issues #29435
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
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
/cc @ArturoAmorQ
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR @lesteve, this is a a really useful contribution. Just a couple of comments but otherwise LGTM :)
Co-authored-by: Arturo Amor <86408019+ArturoAmorQ@users.noreply.github.com>
All right, thanks for the review, let's merge my own PR with 2 approvals. This can always be improved later if the need arises. |
Co-authored-by: Arturo Amor <86408019+ArturoAmorQ@users.noreply.github.com>
Co-authored-by: Arturo Amor <86408019+ArturoAmorQ@users.noreply.github.com>
Following discussion about this at the biweekly meeting, this adds a "Debugging CI issues" to the Developers tips with "Using a lock-file to get an environment close to the CI" as its first entry.