-
Notifications
You must be signed in to change notification settings - Fork 134
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
[IMP] runbot: add troubleshooting documentation #750
base: 16.0
Are you sure you want to change the base?
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.
👍🏻 with minor changes
|
||
## Check batch informations | ||
|
||
The batch view can offer precious informations, like not synchronous commit (the different branches where likely not rebased at the same time, on compatible commits) or the commits are maybe to old. In this case the first action should be to rebase all branches by ensuring to fetch all repo in the same time frame. |
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.
The batch view can offer precious informations, like not synchronous commit (the different branches where likely not rebased at the same time, on compatible commits) or the commits are maybe to old. In this case the first action should be to rebase all branches by ensuring to fetch all repo in the same time frame. | |
The batch view can offer precious informations, like not synchronous commit (the different branches were likely not rebased at the same time, on compatible commits) or the commits are maybe to old. In this case the first action should be to rebase all branches by ensuring to fetch all repo in the same time frame. |
|
||
In some cases a signal between runbot and github, or github and mergebot can be lost on the path (network or github issues most of the time). In this case, a build can be green but the corresponding ci on github or on the mergebot dashboard can be missing. | ||
|
||
There is a action to resend the last commit status of a commit for this purpose. |
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.
There is a action to resend the last commit status of a commit for this purpose. | |
There is an action to resend the last commit status of a commit for this purpose. |
|
||
There is a action to resend the last commit status of a commit for this purpose. | ||
|
||
First access the commit page. Most of the commit sha displayed in the interface are clickable and will lead to the commit page. |
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.
First access the commit page. Most of the commit sha displayed in the interface are clickable and will lead to the commit page. | |
First access the commit page. Most of the commit sha1 hashes displayed in the interface are clickable and will lead to the commit page. |
No description provided.