How should one report GitLab CI bugs?
I'm thinking of two types of bugs.
1. Wine test bugs that specifically happen on the GitLab CI infrastructure. See for instance bug 54334 which describes a set of qasf:asfreader failures that has, so far, only been seen in the Linux GitLab CI.
I'm thinking some Wine developers may be particularly interested in getting such bugs fixed and thus would want to have a way to find them.
Would a 'gitlabci' or just 'ci' keyword be appropriate?
2. Bugs and missing features in the GitLab CI infrastructure itself.
For instance the failures that gitlab-win10-21h2 gets in the ole32:clipboard, riched20:richole and user32:msg tests strongly suggest that the AMD driver was installed with its Adrenalin GUI. Since it is known to interfere with the clipboard this could be considered a bug in that Windows 10 VM configuration. (Alternatively one could argue the tests should be modified to be resistant to such interference which would move this issue to the first category.)
Which product should one pick in Bugzilla for reporting such bugs? They would not fit in 'Wine' product or any of the other existing products except 'Wine-Testbot' if one considers the GitLab CI to be the new TestBot (though I think that would be quite confusing).
-
Francois Gouget