Fix web display of merge trains

[rudymatela]

Closes: #162 Closes: #163

This PR fixes the web display of merge trains:

• [x] display PRs in the order they were approved which is the order of the train (closes #162);
• [x] display speculative rebase failures (closes #163);
• [x] refactor WebInterface to remove repeated code with the classifiedPullRequests function;
• [x] different icons and text for all possible integration statuses: 🟡❌✅ 🔷❗;
• [x] add some automated tests to classifiedPullRequests;
• [x] take screenshots and place them here;

---

Before merge actions (unchanged)

:arrow_up: Nothing changes when all PRs are waiting for review.

These PRs were approved in the following order:

• #141
• #143
• #142
• #144
• #140

---

Before (repository view)

:arrow_up: note PR #142 (Squidward) is missing and PRs are not listed in order of approval.

---

After (repository view)

:arrow_up: correct order, no duplicates, icons

---

Before (global view)

:arrow_up: note PR #142 (Squidward) is missing and PRs are not listed in order of approval. There is one PR that is duplicate!

---

After (global view)

:arrow_up: correct order, no duplicates, icons

---

[rudymatela]

There were changes on master. Better rebase now than later...

[rudymatela]

This is ready for review.

@frank-channable or @alex-mckenna can either of you please review? (whoever is free first -- first-come-first-merged)

[rudymatela]

The emoji indicators are cute, but as we have more they become less obvious. The blue diamond for promoted feels odd, but I can't think of a good choice for this. Text only also has problems though, because it becomes a bit more difficult to just scan the page with your eyes... What do you think?

It does feel hard to parse in the case I presented. However in practice we expect to seldom encounter icons other than :yellow_circle: and :x::

• :heavy_check_mark: - this will only appear if the build of the second/third/etc PRs in the train terminates before the build of the first. This does happen in practice if builds are started almost at the same time, but usually the first PR would be about to finish building. So this should only be in place for brief window;
• :exclamation: :exclamation: Since the start of the month, rebase failures have only happened 17 times. That's 0.68 times per day taking into account all 26 projects we track. If we open the global view and scroll to the page, we expect to see one for a few hours once every couple of days.
• :exclamation: merge rejections due to wrong target branch have happened only once this month!
• :large_blue_diamond: As soon as a PR is promoted, it is deleted from the Hoff state. So I don't expect this to appear in the UI actually. I've put the option there in case we end up displaying it (by accident or by future decision). I've added a comment noting this.

The interface state shown here is a bit of an extreme example illustrating all states:

In practice we normally see something like:

• Building
  • ... :yellow_circle:
  • ... :yellow_circle:
  • ... :yellow_circle:
• Failed
  • ... :x:
  • ... :x:
  • ... :x:
  • ... :x:

Other icons will be more like exceptions:

• Building
  • ... :yellow_circle:
  • ... :yellow_circle:
  • ... :yellow_circle:
• Failed
  • ... :x:
  • ... :x:
  • ... :exclamation: incorrect base branch
  • ... :x:

... or only shown during a brief window:

• Building
  • ... :yellow_circle:
  • ... :heavy_check_mark:
  • ... :yellow_circle:
• Failed
  • ... :x:
  • ... :x:
  • ... :x:
  • ... :x:

PS: here are the two queries:

journalctl -u hoff -S2022-08-01 | grep "Posted.*Failed to rebase"
journalctl -u hoff -S2022-08-01 | grep "Posted.*Merge rejected:"

[alex-mckenna]

Hmm, okay. That seems reasonable then. Thanks for adding the comment :+1:

PS: Good to know, you don't need sudo for those commands by the way

[rudymatela]

@alex-mckenna Thanks for the review. :tada:

@OpsBotPrime merge :ship: :shipit: :rocket:

[OpsBotPrime]

Pull request approved for merge by @rudymatela, rebasing now.

[OpsBotPrime]

Rebased as 00dd4adcb0c1b46ef16426c8a1b15b29a8667327, waiting for CI …

[OpsBotPrime]

CI job :yellow_circle: started.