Hello Noé,
> Next up, we are going to create issues for failing system tests and > assign them to teams where appropriate. Team members, your help in > fixing the tests will be appreciated! Regarding failing system tests, I have a branch that could be handy here[1]. It provides: - A run-system-tests.scm script that is called through the usual "make check-system" command but gives a cleaner output, with individual test logs going to dedicated files[2]. --8<---------------cut here---------------start------------->8--- Running activation (1/151): OK Running agate (2/151): OK Running anonip (3/151): OK Running archlinux-install (4/151): OK Running basic (5/151): OK Running bffe (6/151): OK Running bitlbee (7/151): OK ... --8<---------------cut here---------------end--------------->8--- It also allows to skip certain tests, or to execute a subset of the tests. - The branch also works around the issue that is presented here[3], where the Guix derivations is computed for every single system test, making the process of running all system tests quite painful. For now the work-around consists in reverting 94c9e53fa, but I am sure there's a better way. The run-system-tests.scm script mentioned above also makes sure that the same Guix package is used everywhere with the "current-guix-package" parameter. That's the strategy that is used when evaluating system tests for Cuirass. I do not think that I have the bandwidth to make all of that go upstream, but it could be helpful for people working on system tests for the release :) Thanks, Mathieu [1]: https://codeberg.org/guix/guix/src/branch/wip-fix-system-tests. [2]: https://codeberg.org/guix/guix/issues/990 [3]: https://codeberg.org/guix/guix/issues/937
