For each of the error entries there could be one or more ways to solve it. Whether it is a mis-configuration, steps missing, or a bug; there should be a way at the error reporting tool to signal how an error can be solved. A solved-by field is suggested and it should be able to receive a text input where instructions or links can be provided to solving the error. More than one solution per error should be allowed. Commenting on the solution or a way to contact the proposer (preferably traceable for others who might have the same doubt) of the solution should also be possible.
I don't want to be a buzzkiller, but this will only ever be useful if: 1. People submit their errors to the tool (not doing so right now) and the tool is able to handle the extra load (we have big performance problems at the moment) 2. People bother adding the solutions (questionable) 3. The tool becomes a reference point for the community to go check on the issues they have (hard to achieve) I would invest effort on creating some kind of automated linking between errors, patches and Bugzilla entries instead, so that 2 happens by itself to some extent.
When we have autobuilder builds that fail with multiple people, often not the authors of the patch which introduced the error, looking at autobuilder logs and the associated error reports it will be highly beneficial to be able to point the observers to a known solution. In the simplest case of being able to link an error to a solution URL this will be an invaluable tool in improving the SWAT process and getting SWAT back on track in the 2.2 timeframe. Our expectation is that SWAT team members (and the maintainers who trigger the builds) will populate the solution field as a regular part of the SWAT process.
(In reply to comment #2) > > Our expectation is that SWAT team members (and the maintainers who trigger > the builds) will populate the solution field as a regular part of the SWAT > process. So this is for the SWAT team to fill: I totally missed that. Thanks for explaining.
No plans to tackle this during 2.4
Swat has been disbanded so closing this as obsolete. We also have a result tool
.