On Thu, 2011-06-16 at 10:59 -0400, Kamil Paral wrote:
This a status report from our current 0.5.0 testing effort:
1. The tests seem to work properly (except for one Koji timeout and
one NoMoreMirrorsRepoError yum error).
2. The number of items in the mailing list increased substantially, because we send one
email for the full.log and one email for every (pretty) log created. Rpmlint equals two
emails, upgradepath may equal to 10-20 emails. The mailing list is not much human readable
now. We can make adjustments if you want. Personally I consider the list as another kind
of storage place and I don't really mind.
Do you know which emails are sent to maintainers who opt-in for emailed
test results? Will they get the overall full.log, or the individual
emails for their package?
3. We have found an issue with koji/bodhi watcher that caused every
test to be scheduled multiple times. When asking Koji/Bodhi takes really long time,
another watcher can be run in parallel. But the subsequent watcher still operates with the
old data, thus resulting in scheduling the same tests as the first one. We have seen this
issue happening also on our current production instance:
- search for
Jskladan already sent an example patch to tflink to examination, I believe a proper patch
will appear on the ML/in git soon if we confirm it fixes the issue.
Excellent, nice turn-around!
4. We have identified an issue where our email reduction does not
work, it does not send email when it is supposed to (when both depchecks pass for an
-updates-testing update). The root cause if not known yet.
I suppose it will take a few days until the problems are identified and fixed.
Thanks for the update Kamil.