| 1 |
On 07/25/2017 07:22 AM, Sergei Trofimovich wrote: |
| 2 |
> 2. Q: How to make arch testing faster and easier? |
| 3 |
> |
| 4 |
> A: - KEYWORDREQ/STABLEREQ bugs not marked as "runtime testing |
| 5 |
> required" will be automatically tested and keyworded. |
| 6 |
> |
| 7 |
> [handwave] automated tinderbox setup would help a lot |
| 8 |
> to now upfront what fails to built, fails tests. |
| 9 |
|
| 10 |
I've had similar thoughts about this and have already been working on |
| 11 |
some tooling for this. |
| 12 |
|
| 13 |
We would need to establish exactly what criteria must be met for an |
| 14 |
automated test to be considered as successful. |
| 15 |
|
| 16 |
Here's a sample report that my tool produces: |
| 17 |
https://dev.gentoo.org/~kensington/tinderbox/sys-apps/dbus/dbus-1.6.18-r1/df017e14-bd68-47e2-9738-554e7ba1cf10.html |
| 18 |
|
| 19 |
In this case, would it be enough that it builds and tests pass? What |
| 20 |
about the QA issues? Do we need someone to review them to determine if |
| 21 |
they should block stabilisation, or if they're even a regression or not? |
Archives