Francois Gouget fgouget@codeweavers.com wrote:
On Fri, 3 Apr 2020, Dmitry Timoshkov wrote: [...]
Even the patches from wine-devel should not be punished by a simple testing service. It should do its job of running the tests, everything else is not its business.
You need to remember the point of the TestBot: it is to automate testing of the patches so Alexandre can save time by not having to deal with patches that are wrong.
That's a somewhat distorted vision of the original Wine testbot: run the tests, and do this job the best way it could do.
That means:
- Verifying the patch applies using the same parameters (fuzzy) that Alexandre uses.
- Verifying that the patch compiles the way Alexandre wants.
- Verifying that the patch does not introduce new failures.
If any of these applies different criteria from what Alexandre does then it means he has to manually duplicate the work of the TestBot.
Are there no other priorites so it's started to look like a project of some really strange and random things? Is it possible to make testbot really useful for *developers*? Otheriwise posting priority requests to wine-devel seem to be a waste of time, if the target tesbot audience is actually only Alexandre.