Speaker
Description
The Mesa CI pipeline is complex and has many issues that are being addressed (see presentation "Addressing Mesa CI pain points (2nd edition): what we've done, and where we are going").
This workshop will be dedicated to discussing outstanding pain points from the presentation, so that we (the CI developers) can make sure you (the CI users = Mesa developers) agree on what these pain points are, and what our plan to address them should be.
The currently known pain points are:
- Reliability of the Marge workflow (unavailable runners, flaky jobs, ...)
- Long waiting times to get your MR tested and landed
- Requirement to use an external script (GitLab web UI missing some buttons to run just the jobs we want)
- Reproducing CI jobs locally
- Updating job expectations (collating results from multiple runs, reducing the size of the flakes lists, failure rate of different tests, ...)
- GPU hangs: how to prevent merging code that sometimes hang the GPU, and how to minimize impact of flaky hangs once the regression is merged
- Game traces: increasing coverage, and access to the game traces & artifacts
- And probably more, so come tell us what is your pain point!
| Code of Conduct | Yes |
|---|---|
| GSoC, EVoC or Outreachy | No |
| In-person or virtual presentation | In-person |
