On 03/25/2011 03:40 AM, Kamil Paral wrote:
----- Original Message -----
> Longest email subject ever :)
We wanted to have crashed message in the subject. OTOH, it doesn't
really work with depcheck, true :-)
That reminds me, what about to a little improvement to depcheck
script to accept a directory path (containing RPMs) instead of dozens
of RPMs mentioned on the command-line? That could improve things a
little bit.
That might be a little more complicated than it sounds since RPMs can be
input to depcheck as either accepted packages or packages to test. The
solution to that could be as simple as having two temp directories: one
for the accepted packages and one for the testing packages.
As long as we're logging the packages involved somewhere, it shouldn't
be a loss in functionality.
I'll take a look at this while I'm in there for the mirror issue. If I
can see something that makes sense, I'll file another ticket since that
issue seems to be separate from the exception being thrown here.
Either way, I agree that having a subject line THAT long is not
incredibly helpful. If we can't find a way to make it shorter by
improving the command's length, I propose that we find a better way to
summarize errors (at least for depcheck) in the subject and keep the
whole thing in the body of the email.
>
>
https://fedorahosted.org/pipermail/autoqa-results/2011-March/096807.html
>
>
> I'm getting a F13 test host set up so I can dig into this unless
> someone else wants to jump on it first.
I think the solution is easy. I see this error message "no more
mirrors to try" from yum when my network connection is down. But it's
interesting we received the logs back. Hmm...
There could also be an issue with the "repositories" created during
depcheck but that will take more investigation. James' comment about
this happening with other tests makes me think that it might indeed be a
network issue, though.
Tim