Re: Test gate failures

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 5 Mar 2018, Randy Barlow wrote:

> On 03/03/2018 11:15 AM, Michael Cronenworth wrote:
> > * F27 Wine 3.3
> >    - "The update can not be pushed: no test results found"
> >    - https://bodhi.fedoraproject.org/updates/FEDORA-2018-fa6f017315
> > * F26 Wine 3.3
> >    - "The update can not be pushed: 1 of 2 required tests not found"
> >    - https://bodhi.fedoraproject.org/updates/FEDORA-2018-c5a0e704d6
> 
> Both of these seem to have failed rpmdeplint, which I believe indicates
> that they are missing dependencies.

Coes not this rather imply that the ** test environment ** 
needs to be well enough stocked to perform tests?  It MIGHT be 
all right to add a BR for each package, but fixing ONCE by 
stocking the test environment with a test time tool 
(/usr/bin/rpmdeplint), only, and socumenting what one may 
count on being present, seems much more straightforward

I must confess also that I don't see that a BR actually would 
persist over into the test harness environment

-- russ herrold
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux