[AutoQA] #325: depcheck: setup tests such that conflicting packages are not tested together

[fedora-badges]

#325: depcheck: setup tests such that conflicting packages are not tested
together
--------------------+-------------------------------------------------------
 Reporter:  tflink  |       Owner:              
     Type:  task    |      Status:  new         
 Priority:  major   |   Milestone:  Future tasks
Component:  tests   |    Keywords:              
--------------------+-------------------------------------------------------
 We have found a couple of issues with depcheck lately where the setup of
 the test causes failures  because of inherent conflicts between packages
 in the same update (#284, #384).

In order to successfully test the dependencies of all packages, we would
 need to setup the runs differently such that we're not testing packages
 that are designed to fail when installed together.

This would probably involve parsing the RPM conflicts during setup and
 changing the set of pending/accepted packages accordingly.

[fedora-badges]

#325: depcheck: setup tests such that conflicting packages are not tested
together
--------------------+-------------------------------------------------------
 Reporter:  tflink  |        Owner:              
     Type:  task    |       Status:  new         
 Priority:  major   |    Milestone:  Future tasks
Component:  tests   |   Resolution:              
 Keywords:          |  
--------------------+-------------------------------------------------------
Old description:
> We have found a couple of issues with depcheck lately where the setup of
> the test causes failures  because of inherent conflicts between packages
> in the same update (#284, #384).
>
> In order to successfully test the dependencies of all packages, we would
> need to setup the runs differently such that we're not testing packages
> that are designed to fail when installed together.
>
> This would probably involve parsing the RPM conflicts during setup and
> changing the set of pending/accepted packages accordingly.

New description:

We have found a couple of issues with depcheck lately where the setup of
 the test causes failures  because of inherent conflicts between packages
 in the same update (#284, #324).

In order to successfully test the dependencies of all packages, we would
 need to setup the runs differently such that we're not testing packages
 that are designed to fail when installed together.

This would probably involve parsing the RPM conflicts during setup and
 changing the set of pending/accepted packages accordingly.

[fedora-badges]

#325: depcheck: setup tests such that conflicting packages are not tested
together
--------------------+-------------------------------------------------------
 Reporter:  tflink  |        Owner:              
     Type:  task    |       Status:  new         
 Priority:  major   |    Milestone:  Future tasks
Component:  tests   |   Resolution:              
 Keywords:          |  
--------------------+-------------------------------------------------------
Comment (by kparal):

The mentioned two tickets are now in Hot Issues milestone. I supposed they
 would be eligible for a hotfix. If the root cause is more complex and
 requires large changes in depcheck, we could:
  1. merge those two tickets as duplicates into this one
  2. move this ticket into "Nice to have soon" milestone if we want to
 target it very soon, in this or (more probably) the next one release
  3. or leave this ticket in "Future tasks" if we are fine with having this
 depcheck problem around for a few months

What do you think?

[fedora-badges]

#325: depcheck: setup tests such that conflicting packages are not tested
together
--------------------+-------------------------------------------------------
 Reporter:  tflink  |        Owner:              
     Type:  task    |       Status:  new         
 Priority:  major   |    Milestone:  Future tasks
Component:  tests   |   Resolution:              
 Keywords:          |  
--------------------+-------------------------------------------------------
Changes (by sharkcz):

* cc: sharkcz (added)

[fedora-badges]

#325: depcheck: setup tests such that conflicting packages are not tested
together
--------------------+-------------------------------------------------------
 Reporter:  tflink  |        Owner:            
     Type:  task    |       Status:  new       
 Priority:  major   |    Milestone:  Hot issues
Component:  tests   |   Resolution:            
 Keywords:          |  
--------------------+-------------------------------------------------------
Changes (by kparal):

* milestone:  Future tasks => Hot issues

Comment:

Tickets #284 and #324 marked as duplicates of this ticket. Please read
 their description when working on this ticket.

Moving to "Hot issues" milestone. As long as we send Bodhi comment, this
 is an important issue, because we're providing false negative comments to
 a fair number of packages (possible any package with "conflicts"
 dependencies might be affected).

[fedora-badges]

#325: depcheck: setup tests such that conflicting packages are not tested
together
--------------------+-------------------------------------------------------
 Reporter:  tflink  |        Owner:            
     Type:  task    |       Status:  new       
 Priority:  major   |    Milestone:  Hot issues
Component:  tests   |   Resolution:            
 Keywords:          |  
--------------------+-------------------------------------------------------
Comment (by kparal):

Some data to work with: F14+updates contain circa 24 000 RPMs. 366 of
 those contain some "conflicts" dependency: http://fpaste.org/vzve/

Depcheck probably fails only for those 366 (in F14), and only when the
 conflicting packages happen to be in the same test run. When that happens,
 it can also reject some further packages that depend on some packages from
 that 366-set.

[fedora-badges]

#325: depcheck: setup tests such that conflicting packages are not tested
together
--------------------+-------------------------------------------------------
 Reporter:  tflink  |        Owner:          
     Type:  task    |       Status:  new     
 Priority:  major   |    Milestone:  Depcheck
Component:  tests   |   Resolution:          
 Keywords:          |  
--------------------+-------------------------------------------------------
Changes (by kparal):

* milestone:  Hot issues => Depcheck