RFR: 2247: When pr's headHash is missing, stop further processing [v3]

[Erik Joelsson]

On Mon, 29 Apr 2024 23:00:27 GMT, Zhao Song <zsong at openjdk.org> wrote:

>> Kevin Rushforth found this GitLab issue few years ago.
>> 
>> Sometimes, pull requests in GitLab would be stuck. When it happens, it shows the number of commits as "0". Clicking on the "Changes" tab shows no diffs, and displays a warning banner: "Something went wrong on our end. Please try again!" This requires action on user's part to get them "unstuck".
>> 
>> In Skara side, when it happens, pull request bot would not be able to get the headHash of this pull request and then throw an exception and trigger an other round of CheckWorkItem. If the user doesn't fix it, skara bot will continuously work on the pull request.
>> 
>> To resolve it, we should try to make pull request bot be able to identify this situation and provide some guidance to the users.
>
> Zhao Song has updated the pull request incrementally with one additional commit since the last revision:
> 
>   review comment

bots/pr/src/main/java/org/openjdk/skara/bots/pr/CheckWorkItem.java line 434:

> 432: 
> 433:         if (pr.headHash().hex() == null) {
> 434:             String text = "The head hash of this pull request is missing." +

Suggestion:

            String text = "The head hash of this pull request is missing. " +

bots/pr/src/main/java/org/openjdk/skara/bots/pr/CheckWorkItem.java line 436:

> 434:             String text = "The head hash of this pull request is missing." +
> 435:                     "Until this is resolved, this pull request cannot be processed." +
> 436:                     "This is likely caused by a caching problem in the server and can usually be worked around by pushing another commit to the pull request branch. " +

Probably break this line a bit.

-------------

PR Review Comment: https://git.openjdk.org/skara/pull/1645#discussion_r1583892217
PR Review Comment: https://git.openjdk.org/skara/pull/1645#discussion_r1583892431