On Mon, Oct 31, 2022 at 04:36:32PM -0700, Brian Norris wrote: [...]
...but still, it's kinda sad that we've bothered to set up all this "CI" and then nobody paid any attention :( I only noticed because I recently subscribed to chrome-platform@lists.linux.dev.
I do notice that the kernelci reported test failures/regressions for chrome-platform repo. I only raised my hand in some private sessions instead of public mailing lists.
For now, I only see build results (e.g. [1]) as a signal to move patches from "for-kernelci" to "for-next" branches; and ignore the regression ones temporarily.
The LAVA lab "lab-collabora" was setup by Collabora; and it has been un-maintained for a long while. In order to troubleshooting, I thought we need to access the LAVA dispatcher and boards (at least from SSH). But it seems only Collabora folks have the permission to access them.
In either cases, we should figure out a way to make the "CI" back to work. I will seek for Collabora folks' help.
[1]: https://lore.kernel.org/chrome-platform/63609caf.620a0220.bd35e.9c8e@mx.goog...