File: debug-ci-failures.rst

package info (click to toggle)
ironic 1%3A21.1.0-3
  • links: PTS, VCS
  • area: main
  • in suites: bookworm
  • size: 18,704 kB
  • sloc: python: 151,217; sh: 3,175; pascal: 709; xml: 369; makefile: 79
file content (30 lines) | stat: -rw-r--r-- 1,074 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
.. _debug-ci-failures:

=====================
Debugging CI failures
=====================


If you see `FAILURE` in one or more jobs for your patch please don't panic.
This guide may help you to find the initial reason for the failure.
When clicking in the failed job you will be redirect to the Zuul web page that
contains all the information about the job build.


Zuul Web Page
=============

The page has three tabs: `Summary`, `Logs` and `Console`.

* Summary: Contains overall information about the build of the job, if the job
  build failed it will contain a general output of the failure.

* Logs:  Contains all configurations and log files about all services that
  were used in the job. This will give you an overall idea of the failures and
  you can identify services that may be involved. The `job-output` file can
  give an overall idea of the failures and what services may be involved.

* Console: Contains all the playbooks that were executed, by clicking in the
  arrow before each playbook name you can find the roles and commands that were
  executed.