Skip to content
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

Open
wants to merge 1 commit into
base: 16.0
Choose a base branch
from

Conversation

Xavier-Do
Copy link
Contributor

No description provided.

@C3POdoo C3POdoo requested a review from a team March 24, 2023 11:19
Copy link
Contributor

@d-fence d-fence left a 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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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.

@Xavier-Do Xavier-Do changed the base branch from 15.0 to 16.0 June 22, 2023 13:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants