mesa-ci-status: parse job traces and classify under categories (finished / didn't finished)
Add ComputeJobsExtraInfo to handle extra request of jobs. Collect, handle traces and show results in the report. Bump the container tag to re-generate the image (since a new packaged was added in requirements.txt)
traces are configured through traces_config.yaml the file has the format:
categories:
- name: error category name 1
patterns:
- pattern 1
- pattern 2
- name: error category name 2
patterns:
- pattern 1
- pattern 2The order matters, the job will be classified in the first category it fits in.
Example:
PERIOD: Daily report for Thu Apr 14 2022
FAILED MERGE PIPELINES: 8/24 - 33.33%
FAILED JOBS: 49/2078 - 2.36%
TOP 10 FAILING JOBS:
| job name | number of failures |
|---|---|
| windows_build_vs2019 | 3 |
| test-dozen-deqp | 2 |
| test-spirv2dxil-windows | 1 |
| test-d3d12-quick_shader | 1 |
| test-d3d12-quick_gl | 1 |
| softpipe-asan-gles31 | 1 |
| softpipe | 1 |
| panfrost-g72-gl:arm64 3/3 | 1 |
| panfrost-g72-gl:arm64 2/3 | 1 |
| panfrost-g72-gl:arm64 1/3 | 1 |
ERRORS PER CATEGORY (TOP 10):
| error category | number of occurrences |
|---|---|
| Job finished | 35 |
| Job didn't finished - Job's log exceeded limit | 8 |
| Job didn't finished - Other | 6 |
FAILED JOBS (limited to 100 entries):
INFORMATION: All numbers only considers mesa/mesa. Pipelines with updated_at < 2022-04-14 and jobs with finished_at < 2022-04-14 were ignored. FAILED MERGE PIPELINES: Calculated from finished pipelines triggered by Marge in a merge requests. Counted when a pipeline contains a failed job, even if it got retried and the pipeline passed (status success). FAILED JOBS: Consider jobs from the same pipelines from FAILED MERGE PIPELINES.