d041630a37
The new runner reduces the runtime by about 1/3 thanks to using rust instead of python, and includes automatic flake handling so you don't just have to skip flaky tests. The wrapper script also includes IRC flake reporting (so one can track and update the flakes list to improve CI reliability), always uploading results to CI for review (so you can diagnose flakes and look at timings), has a prettier regressions report and a helpful timing report, and is the same as what's used by all the HW runners as well. The downside is that by dropping the massive list of skips, you no longer get flagged if Mesa refactors end up accidentally disabling extensions and thus making tests skip. For that, I've started on https://gitlab.freedesktop.org/anholt/deqp-runner/-/merge_requests/33 so that hardware drivers get extension checking coverage too. Thanks to the perf improvement, we get to drop one of the jobs for llvmpipe. xfail lists were mostly sed-jobs from the prior expectations lists. The exceptions to that you'll find in the form of whitespace around the affected test group (usually changes of capitalization or special-characters), or an explanation for the more interesting changes (which thankfully we can now record in the xfails lists!). Reviewed-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/14604> |
||
|---|---|---|
| .gitlab/issue_templates | ||
| .gitlab-ci | ||
| android | ||
| bin | ||
| build-support | ||
| docs | ||
| include | ||
| src | ||
| subprojects | ||
| .dir-locals.el | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .mailmap | ||
| .travis.yml | ||
| CODEOWNERS | ||
| README.rst | ||
| VERSION | ||
| meson.build | ||
| meson_options.txt | ||
README.rst
`Mesa <https://mesa3d.org>`_ - The 3D Graphics Library ====================================================== Source ------ This repository lives at https://gitlab.freedesktop.org/mesa/mesa. Other repositories are likely forks, and code found there is not supported. Build & install --------------- You can find more information in our documentation (`docs/install.rst <https://mesa3d.org/install.html>`_), but the recommended way is to use Meson (`docs/meson.rst <https://mesa3d.org/meson.html>`_): .. code-block:: sh $ mkdir build $ cd build $ meson .. $ sudo ninja install Support ------- Many Mesa devs hang on IRC; if you're not sure which channel is appropriate, you should ask your question on `OFTC's #dri-devel <irc://irc.oftc.net/dri-devel>`_, someone will redirect you if necessary. Remember that not everyone is in the same timezone as you, so it might take a while before someone qualified sees your question. To figure out who you're talking to, or which nick to ping for your question, check out `Who's Who on IRC <https://dri.freedesktop.org/wiki/WhosWho/>`_. The next best option is to ask your question in an email to the mailing lists: `mesa-dev\@lists.freedesktop.org <https://lists.freedesktop.org/mailman/listinfo/mesa-dev>`_ Bug reports ----------- If you think something isn't working properly, please file a bug report (`docs/bugs.rst <https://mesa3d.org/bugs.html>`_). Contributing ------------ Contributions are welcome, and step-by-step instructions can be found in our documentation (`docs/submittingpatches.rst <https://mesa3d.org/submittingpatches.html>`_). Note that Mesa uses gitlab for patches submission, review and discussions.