Provide early feedback when a patch has job failures
Closed, ResolvedPublic
Actions

Assigned To

Authored By

	kostajh
	Nov 24 2022, 7:51 AM

Description

Following up from the declined T225871: Selenium and PHPUnit: Stop execution on failure and tangential to T248531: Abort a Zuul pipeline when one job completed with failures (change zuul scheduler's failure check from areAllJobsComplete to didAnyJobFail):

have a web app on toolforge, i.e. early-warning-bot.toolforge.org https://wikitech.wikimedia.org/wiki/Tool:Early_warning_bot
patch Quibble so that when a process ends with exit code other than 0, it POSTs some data about the job (patch details) to the web app
the web app adds a comment and a Verified -1 to the patch
- the comment should include a link to the Jenkins build URL for the failing job
Quibble could capture a formatted version of the failing command output, and include this in the comment that the web app leaves in Gerrit. That is related to T209149: Have linters/tests results show up as comments in files on gerrit. We'd need a trimmed version of this for PHPUnit which currently dumps a lot of text. See T331061: Capture output from failed command and transmit to earlywarningbot

Why?

developers receive pings early via email/IRC that a patch has failures. Yes, you can watch Zuul, but most people don't know to do that, and it doesn't notify you that a job has failed.
Early feedback on a failed patch allows the developer to 1) fix the patch before switching their context to other things or 2) in a backport situation, know that they need to restart the jobs

Details

Subject	Repo	Branch	Lines +/-
build: Add quibble.yaml and enable Early Warning Bot feedback	mediawiki/core	master	+4 -0
build: Add quibble.yaml and enable early warning bot feedback	mediawiki/extensions/AbuseFilter	master	+2 -0
build: Add quibble.yaml and enable early warning bot feedback	mediawiki/extensions/MediaModeration	master	+3 -0
build: Add quibble.yaml and enable early warning bot feedback	mediawiki/extensions/ReportIncident	master	+3 -0
build: Add quibble.yaml and enable early warning bot feedback	mediawiki/extensions/CheckUser	master	+2 -0
build: Add quibble.yaml and enable early warning bot feedback	mediawiki/extensions/Echo	master	+3 -0
release: Quibble 1.5.2	integration/quibble	master	+10 -1
reporting: Command name can be a string	integration/quibble	master	+9 -4
build: Add quibble.yaml	mediawiki/extensions/GrowthExperiments	master	+3 -0
reporting: Add documentation for quibble.yaml	integration/quibble	master	+24 -0
reporting: Remove slash from build URL	integration/quibble	master	+1 -1
jjb: Enable --reporting-url for more Quibble jobs	integration/config	master	+10 -10
jjb: Enable reporting-url for quibble-{packages-source}-{database}-{php}-docker	integration/config	master	+1 -1
jjb: switch jobs to Quibble 1.5.0	integration/config	master	+23 -23
jjb: Enable reporting-url for quibble-{packages-source}-{database}-{php}-docker	integration/config	master	+1 -1
jjb: add QUIBBLE_API_KEY to Quibble jobs	integration/config	master	+81 -0
dockerfiles: update to Quibble 1.5.0	integration/config	master	+55 -1
release: Quibble 1.5.0	integration/quibble	master	+20 -3
Allow sending build failure data to external endpoint	integration/quibble	master	+138 -9

Related Objects
Search...

Status	Assigned	Task
Resolved	kostajh	T323750 Provide early feedback when a patch has job failures
Declined	None	T330741 Create customized Gerrit label for "All-Jobs-Passed"
Resolved	kostajh	T330749 earlywarningbot: Provide instructions for "recheck"
Resolved	kostajh	T330750 Quibble: Include the failed command in data passed to external endpoint
Resolved	kostajh	T331061 Capture output from failed command and transmit to earlywarningbot
Resolved	Urbanecm_WMF	T331236 Exclude certain jobs from early feedback
Open	None	T331996 Quibble: Generate structured output for command success/failures
Open	None	T332178 Run MediaWiki core/skin/extension Phan jobs via Quibble
Open	None	T332179 Run MediaWiki core/skin/extension mwgate-node16 jobs via Quibble

Event Timeline

There are a very large number of changes, so older changes are hidden. Show Older Changes

gerritbot added a project: Patch-For-Review.Dec 8 2022, 2:11 PM

Change 866376 merged by jenkins-bot:

[integration/quibble@master] Allow sending build failure data to external endpoint

https://gerrit.wikimedia.org/r/866376

Maintenance_bot removed a project: Patch-For-Review.Feb 21 2023, 12:30 PM

Change 890809 had a related patch set uploaded (by Kosta Harlan; author: Kosta Harlan):

[integration/quibble@master] release: Quibble 1.5.0

https://gerrit.wikimedia.org/r/890809

gerritbot added a project: Patch-For-Review.Feb 21 2023, 12:53 PM

Change 890809 merged by jenkins-bot:

[integration/quibble@master] release: Quibble 1.5.0

https://gerrit.wikimedia.org/r/890809

Maintenance_bot removed a project: Patch-For-Review.Feb 21 2023, 1:29 PM

Change 890817 had a related patch set uploaded (by Hashar; author: Hashar):

[integration/config@master] dockerfiles: update to Quibble 1.5.0

https://gerrit.wikimedia.org/r/890817

gerritbot added a project: Patch-For-Review.Feb 21 2023, 1:46 PM

Change 890817 merged by jenkins-bot:

[integration/config@master] dockerfiles: update to Quibble 1.5.0

https://gerrit.wikimedia.org/r/890817

Maintenance_bot removed a project: Patch-For-Review.Feb 21 2023, 2:10 PM

Next step is to create QUIBBLE_API_KEY for use with quibble jobs (similar to SONAR_API_KEY) and I can add it to the config used by the application on https://earlywarningbot.toolforge.org. After that, projects tested by Quibble can use a quibble.yaml file to allow for comments and/or verification -1 votes as soon as a single job fails in a build.

We can store the key in Jenkins credentials store then inject it as QUIBBLE_API_KEY in the Quibble jobs using the Credentials Binding plugin. We have done something similar for COMPOSER_GITHUB_OAUTHTOKEN. In jjb that looks like:

- job:
    wrappers:
      - credentials-binding:
          - text:
              credential-id: composer-github-oauthtoken
              variable: COMPOSER_GITHUB_OAUTHTOKEN

I have added the API key to the Jenkins credential store with the id quibble-earlywarningbot-api-key (private link https://integration.wikimedia.org/ci/manage/credentials/store/system/domain/_/credential/quibble-earlywarningbot-api-key/ ).

Change 891276 had a related patch set uploaded (by Kosta Harlan; author: Kosta Harlan):

[integration/quibble@master] reporting: Add documentation for quibble.yaml

https://gerrit.wikimedia.org/r/891276

gerritbot added a project: Patch-For-Review.Feb 22 2023, 2:00 PM

Change 891278 had a related patch set uploaded (by Hashar; author: Hashar):

[integration/config@master] jjb: add QUIBBLE_API_KEY to Quibble jobs

https://gerrit.wikimedia.org/r/891278

Mentioned in SAL (#wikimedia-releng) [2023-02-22T14:19:27Z] <hashar> Updating all jobs to add QUIBBLE_API_KEY to the Quibble jobs | https://gerrit.wikimedia.org/r/c/integration/config/+/891278/ | T323750

Change 891278 merged by jenkins-bot:

[integration/config@master] jjb: add QUIBBLE_API_KEY to Quibble jobs

https://gerrit.wikimedia.org/r/891278

Change 891514 had a related patch set uploaded (by Kosta Harlan; author: Kosta Harlan):

[integration/config@master] jjb: Enable reporting-url for quibble-{packages-source}-{database}-{php}-docker

https://gerrit.wikimedia.org/r/891514

Change 891514 merged by jenkins-bot:

[integration/config@master] jjb: Enable reporting-url for quibble-{packages-source}-{database}-{php}-docker

https://gerrit.wikimedia.org/r/891514

Change 891548 had a related patch set uploaded (by Hashar; author: Hashar):

[integration/config@master] jjb: switch jobs to Quibble 1.5.0

https://gerrit.wikimedia.org/r/891548

Change 891549 had a related patch set uploaded (by Hashar; author: Kosta Harlan):

[integration/config@master] jjb: Enable reporting-url for quibble-{packages-source}-{database}-{php}-docker

https://gerrit.wikimedia.org/r/891549

Change 891548 merged by jenkins-bot:

[integration/config@master] jjb: switch jobs to Quibble 1.5.0

https://gerrit.wikimedia.org/r/891548

Change 891549 merged by jenkins-bot:

[integration/config@master] jjb: Enable reporting-url for quibble-{packages-source}-{database}-{php}-docker

https://gerrit.wikimedia.org/r/891549

Change 891559 had a related patch set uploaded (by Kosta Harlan; author: Kosta Harlan):

[integration/config@master] jjb: Enable --reporting-url for more Quibble jobs

https://gerrit.wikimedia.org/r/891559

Change 891559 merged by jenkins-bot:

[integration/config@master] jjb: Enable --reporting-url for more Quibble jobs

https://gerrit.wikimedia.org/r/891559

Change 891653 had a related patch set uploaded (by Kosta Harlan; author: Kosta Harlan):

[integration/quibble@master] reporting: Remove slash from build URL

https://gerrit.wikimedia.org/r/891653

Change 891653 merged by jenkins-bot:

[integration/quibble@master] reporting: Remove slash from build URL

https://gerrit.wikimedia.org/r/891653

Change 891276 merged by jenkins-bot:

[integration/quibble@master] reporting: Add documentation for quibble.yaml

https://gerrit.wikimedia.org/r/891276

Maintenance_bot removed a project: Patch-For-Review.Feb 24 2023, 2:10 PM

hashar assigned this task to kostajh.Feb 28 2023, 9:24 AM

kostajh closed subtask T330741: Create customized Gerrit label for "All-Jobs-Passed" as Declined.Feb 28 2023, 10:55 AM

kostajh mentioned this in Blog Post: CI: Get notified immediately when a job fails.Mar 3 2023, 12:44 PM

Change 867531 had a related patch set uploaded (by Kosta Harlan; author: Kosta Harlan):

[mediawiki/extensions/GrowthExperiments@master] build: Add quibble.yaml

https://gerrit.wikimedia.org/r/867531

gerritbot added a project: Patch-For-Review.Mar 3 2023, 1:06 PM

Change 867531 merged by jenkins-bot:

[mediawiki/extensions/GrowthExperiments@master] build: Add quibble.yaml

https://gerrit.wikimedia.org/r/867531

ReleaseTaggerBot added a project: MW-1.40-notes (1.40.0-wmf.26; 2023-03-06).Mar 4 2023, 11:00 AM

Maintenance_bot removed a project: Patch-For-Review.Mar 4 2023, 11:10 AM

Change 894216 had a related patch set uploaded (by Kosta Harlan; author: Kosta Harlan):

[integration/quibble@master] reporting: Command name can be a string

https://gerrit.wikimedia.org/r/894216

gerritbot added a project: Patch-For-Review.Mar 5 2023, 7:43 PM

Change 894535 had a related patch set uploaded (by Kosta Harlan; author: Kosta Harlan):

[integration/quibble@master] release: Quibble 1.5.2

https://gerrit.wikimedia.org/r/894535

Change 894216 merged by jenkins-bot:

[integration/quibble@master] reporting: Command name can be a string

https://gerrit.wikimedia.org/r/894216

Change 894535 merged by jenkins-bot:

[integration/quibble@master] release: Quibble 1.5.2

https://gerrit.wikimedia.org/r/894535

Maintenance_bot removed a project: Patch-For-Review.Mar 6 2023, 11:32 AM

Mentioned in SAL (#wikimedia-releng) [2023-03-06T12:14:56Z] <hashar> Tag Quibble 1.5.2 @ 932b48cab06c # T331236 T331061 T323750

Stashbot mentioned this in T331061: Capture output from failed command and transmit to earlywarningbot.Mar 6 2023, 12:15 PM

kostajh closed subtask T330750: Quibble: Include the failed command in data passed to external endpoint as Resolved.Mar 14 2023, 12:52 PM

kostajh closed subtask T331236: Exclude certain jobs from early feedback as Resolved.

kostajh updated the task description. (Show Details)Mar 15 2023, 9:18 AM

kostajh closed subtask T331061: Capture output from failed command and transmit to earlywarningbot as Resolved.Mar 15 2023, 1:43 PM

kostajh closed subtask T330749: earlywarningbot: Provide instructions for "recheck" as Resolved.

Change 904759 had a related patch set uploaded (by Kosta Harlan; author: Kosta Harlan):

[mediawiki/extensions/Echo@master] build: Add quibble.yaml and enable early warning bot feedback

https://gerrit.wikimedia.org/r/904759

gerritbot added a project: Patch-For-Review.Mar 31 2023, 9:43 AM

Change 904759 merged by jenkins-bot:

[mediawiki/extensions/Echo@master] build: Add quibble.yaml and enable early warning bot feedback

https://gerrit.wikimedia.org/r/904759

Maintenance_bot removed a project: Patch-For-Review.Apr 4 2023, 11:10 PM

ReleaseTaggerBot added a project: MW-1.41-notes (1.41.0-wmf.4; 2023-04-10).Apr 5 2023, 3:00 AM

It seems like the early warning bot is not responding to the recheck command: https://gerrit.wikimedia.org/r/c/mediawiki/extensions/GrowthExperiments/+/911912

In T323750#8810590, @Tgr wrote:

It seems like the early warning bot is not responding to the recheck command: https://gerrit.wikimedia.org/r/c/mediawiki/extensions/GrowthExperiments/+/911912

Yeah, this is noted in https://wikitech.wikimedia.org/wiki/Tool:Early_warning_bot#Known_issues and the bot also leaves a comment to that effect, e.g. in https://gerrit.wikimedia.org/r/c/mediawiki/extensions/GrowthExperiments/+/908359/19#message-68476447ee66633c2f42a8b3405ee53031c68a9e

Failed command: "composer run --timeout=0 phpunit:entrypoint -- --testsuite extensions --group Database --exclude-group Broken,ParserFuzz,Stub,Standalone"
Details: https://integration.wikimedia.org/ci/job/quibble-vendor-mysql-php74-noselenium-docker/96300/consoleFull

Note: If the build failed due to a non-deterministic test, please manually remove the "Verified: -1" vote after submitting a "recheck" comment.

Maybe setting the "Verified" label is not that useful, and we should remove it as an option. A workaround is to set should_vote: 0 (or remove that line entirely) in the extension's quibble.yaml.

I wonder if there's some way to preprocess red/green output control characters?

[0m  GET quickstarttips[0m
  [32m  [32m✔[39m[0m[90m the copyedit response has the correct shape and parameters substituted[0m[31m (1130ms)[0m
  [32m  [32m✔[39m[0m[90m loads different messages varying by skin[0m[31m (104ms)[0m
  [32m  [32m✔[39m[0m[90m should get tips for minerva / wikitext / update without an HTTP error[0m[33m (75ms)[0m
  [31m  1) should get tips for minerva / wikitext / expand without an HTTP error[0m
  [32m  [32m✔[39m[0m[90m should get tips for minerva / wikitext / references without an HTTP error[0m[31m (762ms)[0m
[92m [0m[32m 37 passing[0m[90m (6s)[0m
[31m  1 failing[0m

takes a moment to understand.

Tgr awarded a token.May 15 2023, 2:22 PM

In T323750#8850637, @Tgr wrote:

I wonder if there's some way to preprocess red/green output control characters?

[0m  GET quickstarttips[0m
  [32m  [32m✔[39m[0m[90m the copyedit response has the correct shape and parameters substituted[0m[31m (1130ms)[0m
  [32m  [32m✔[39m[0m[90m loads different messages varying by skin[0m[31m (104ms)[0m
  [32m  [32m✔[39m[0m[90m should get tips for minerva / wikitext / update without an HTTP error[0m[33m (75ms)[0m
  [31m  1) should get tips for minerva / wikitext / expand without an HTTP error[0m
  [32m  [32m✔[39m[0m[90m should get tips for minerva / wikitext / references without an HTTP error[0m[31m (762ms)[0m
[92m [0m[32m 37 passing[0m[90m (6s)[0m
[31m  1 failing[0m

takes a moment to understand.

@hashar do you have any ideas? I'm not sure what to do about it.

In T323750#8851057, @kostajh wrote:

In T323750#8850637, @Tgr wrote:

I wonder if there's some way to preprocess red/green output control characters?

[0m  GET quickstarttips[0m
  [32m  [32m✔[39m[0m[90m the copyedit response has the correct shape and parameters substituted[0m[31m (1130ms)[0m
  [32m  [32m✔[39m[0m[90m loads different messages varying by skin[0m[31m (104ms)[0m
  [32m  [32m✔[39m[0m[90m should get tips for minerva / wikitext / update without an HTTP error[0m[33m (75ms)[0m
  [31m  1) should get tips for minerva / wikitext / expand without an HTTP error[0m
  [32m  [32m✔[39m[0m[90m should get tips for minerva / wikitext / references without an HTTP error[0m[31m (762ms)[0m
[92m [0m[32m 37 passing[0m[90m (6s)[0m
[31m  1 failing[0m

takes a moment to understand.

@hashar do you have any ideas? I'm not sure what to do about it.

I'll have a look at https://github.com/TheLarkInn/ansi-regex

Writing a regex shouldn't be hard IMO (we really only care about those two colors), the harder question is how to convey the information to the user? (Unless Gerrit provides some way for bots to write HTML comments.)

In T323750#8852326, @Tgr wrote:

Writing a regex shouldn't be hard IMO (we really only care about those two colors), the harder question is how to convey the information to the user? (Unless Gerrit provides some way for bots to write HTML comments.)

We could replace the green/red with ✅ and ❌, which is what the sonarqube bot does.

I don't think we should attempt to parse output intended for humans, it causes troubles (like ansi codes) and is prone to change upon time as the various test utilities slightly change their output. Instead the test commands should output some JUnit / Json blob which should be stable over time and by easy to parse.

Both Karma for QUnit tests and webdriver.io for Selenium tests must have reporters for that. We used to collect PHPUnit tests in JUnit format but we got rid of that cause the formatted tests results were not directly reachable by developers since CI points to the console rather than page of the Jenkins build. They also took a lot of disk space on the Jenkins primary, then I guess we could add some processing after the build has completed to only retain non success tests which will shrink the resulting JUnit/Json file.

Once we get our tests runners to output some Json, we can get Gerrit to fetch the blobs from the Jenkins builds and exposes them via its https://gerrit.wikimedia.org/r/Documentation/pg-plugin-checks-api.html Checks API. The API is further described as TypeScript interfaces at https://gerrit.googlesource.com/gerrit/+/stable-3.5/polygerrit-ui/app/api/checks.ts as CheckResult.CodePointer but it seems to be better suited for linters.

So the idea is to have CI / Jenkins to expose the tests in json, get the Javascript to retrieve it and format it according to the checks.ts interface and Gerrit will happily format them under the Check tab. The thing is a CheckResult merely has a string result and does not have a finer grained way to expose individual tests failures :/

A past exchange with upstream:

https://discord.com/channels/775374026587373568/1019941974842806302/1078245868353892362

Antoine: hi, I have a question about the check API, what is CodePointers for? It is an array which should hint at file/lines having an issue, but the comment at https://gerrit.googlesource.com/gerrit/+/master/polygerrit-ui/app/api/checks.ts#413 states only one pointer is supported. Thus if a check reports errors on multiple files / lines, we would only get one shown? I am not sure how it is related to the "Findings" tab
the code does invoke map on the array, so maybe the comment is misleading

https://discord.com/channels/775374026587373568/1019941974842806302/1078267881982275624

brohlfs:
Only one codePointer is supported atm.
If you provide a codePointer, then the check result is shown inline in the diff: https://imgur.com/a/HeLespU
If a check run reports mulitple errors, then the recommendation is to use multiple check results, and attach one code pointer to each result.
The "Findings" tab is for robot comments. We have tentative plans for retiring robot comments in favor of check results with code pointers.
Let me know if you have more questions. Happy to help!

https://imgur.com/a/HeLespU :

I have found an example on Chromium https://chromium-review.googlesource.com/c/chromium/src/+/4513944?tab=checks though I don't know they render it with some nice HTML since the message is supposedly a raw text interpreted as Gerrit markdown subset :(

gerrit_chromium_test_failure.png (684×1 px, 156 KB)

Change 931995 had a related patch set uploaded (by Kosta Harlan; author: Kosta Harlan):

[mediawiki/extensions/CheckUser@master] build: Add quibble.yaml and enable early warning bot feedback

https://gerrit.wikimedia.org/r/931995

gerritbot added a project: Patch-For-Review.Jun 21 2023, 7:53 PM

Change 931995 merged by jenkins-bot:

[mediawiki/extensions/CheckUser@master] build: Add quibble.yaml and enable early warning bot feedback

https://gerrit.wikimedia.org/r/931995

ReleaseTaggerBot edited projects, added MW-1.41-notes (1.41.0-wmf.15; 2023-06-27); removed MW-1.41-notes (1.41.0-wmf.4; 2023-04-10).Jun 21 2023, 10:00 PM

Maintenance_bot removed a project: Patch-For-Review.Jun 21 2023, 10:10 PM

Change 963309 had a related patch set uploaded (by Kosta Harlan; author: Kosta Harlan):

[mediawiki/extensions/ReportIncident@master] build: Add quibble.yaml and enable early warning bot feedback

https://gerrit.wikimedia.org/r/963309

gerritbot added a project: Patch-For-Review.Oct 4 2023, 1:32 PM

Change 963309 merged by jenkins-bot:

[mediawiki/extensions/ReportIncident@master] build: Add quibble.yaml and enable early warning bot feedback

https://gerrit.wikimedia.org/r/963309

kostajh mentioned this in rEREI38418db4d211: build: Add quibble.yaml and enable early warning bot feedback.Oct 4 2023, 2:36 PM

ReleaseTaggerBot edited projects, added MW-1.41-notes (1.41.0-wmf.30; 2023-10-10); removed MW-1.41-notes (1.41.0-wmf.15; 2023-06-27).Oct 4 2023, 3:00 PM

Maintenance_bot removed a project: Patch-For-Review.Oct 4 2023, 3:11 PM

Change 965391 had a related patch set uploaded (by Kosta Harlan; author: Kosta Harlan):

[mediawiki/extensions/MediaModeration@master] build: Add quibble.yaml and enable early warning bot feedback

https://gerrit.wikimedia.org/r/965391

gerritbot added a project: Patch-For-Review.Oct 12 2023, 6:52 AM

Change 965391 merged by jenkins-bot:

[mediawiki/extensions/MediaModeration@master] build: Add quibble.yaml and enable early warning bot feedback

https://gerrit.wikimedia.org/r/965391

Maintenance_bot removed a project: Patch-For-Review.Oct 12 2023, 12:10 PM

ReleaseTaggerBot added a project: MW-1.42-notes (1.42.0-wmf.1; 2023-10-17).Oct 12 2023, 1:00 PM

Change 971120 had a related patch set uploaded (by Kosta Harlan; author: Kosta Harlan):

[mediawiki/core@master] build: Add quibble.yaml and enable Early Warning Bot feedback

https://gerrit.wikimedia.org/r/971120

gerritbot added a project: Patch-For-Review.Nov 2 2023, 10:20 AM

kostajh closed this task as Resolved.Nov 10 2023, 10:10 AM

Tgr mentioned this in T225730: Reduce runtime of MW shared gate Jenkins jobs to 5 min.Feb 12 2024, 3:01 PM

Change #1030086 had a related patch set uploaded (by Kosta Harlan; author: Kosta Harlan):

[mediawiki/extensions/AbuseFilter@master] build: Add quibble.yaml and enable early warning bot feedback

https://gerrit.wikimedia.org/r/1030086

kostajh mentioned this in T366763: Leave a comment on the Gerrit change when it is scheduled for a backport.Jun 6 2024, 7:43 AM

Change #1030086 merged by jenkins-bot:

[mediawiki/extensions/AbuseFilter@master] build: Add quibble.yaml and enable early warning bot feedback

https://gerrit.wikimedia.org/r/1030086

ReleaseTaggerBot added a project: MW-1.43-notes (1.43.0-wmf.12; 2024-07-02).Jun 26 2024, 1:00 PM

Mentioned in SAL (#wikimedia-releng) [2024-07-11T19:03:57Z] <hashar> gerrit: added EarlyWarningBot to the Service Users group | T323750

hashar mentioned this in T368883: Allow fixsuggesterbot to use the edit API endpoint.Jul 11 2024, 7:07 PM

Change #971120 abandoned by Hashar:

[mediawiki/core@master] build: Add quibble.yaml and enable Early Warning Bot feedback

https://gerrit.wikimedia.org/r/971120

Maintenance_bot removed a project: Patch-For-Review.Oct 21 2024, 9:30 AM

	F37000765: gerrit_chromium_test_failure.png
	May 16 2023, 10:27 AM

	F35814298: Zuul 2.5 report in Gerrit Checks UI
	Nov 24 2022, 8:29 AM

	F35810854: zuul_status_in_gerrit.png
	Nov 24 2022, 8:29 AM
	File Not Attached

Provide early feedback when a patch has job failuresClosed, ResolvedPublicActions

Description

Details

Related ObjectsSearch...

Event Timeline

Provide early feedback when a patch has job failures
Closed, ResolvedPublic
Actions

Related Objects
Search...