#284: depcheck does not produce output for some pending updates
--------------------+-------------------------------------------------------
 Reporter:  kparal  |        Owner:            
     Type:  defect  |       Status:  reopened  
 Priority:  major   |    Milestone:  Hot issues
Component:  tests   |   Resolution:            
 Keywords:          |  
--------------------+-------------------------------------------------------
Comment (by jlaska):

 Replying to [comment:8 kparal]:
 > I reviewed that. My greatest concern is whether we can rely on depcheck
 output when some builds were not evaluated correctly.

 ff crashes for me when attempting to reply in reviewboard.  I'll reply
 here ...

 > The code itself seems fine. But it will have a side effect - updates
 with builds
 > with no depcheck output will be reported to Bodhi as NEEDS_INSPECTION.
 Is that
 > desired? My first thought would be not to send reports, when we have
 nothing to
 > report.

 Hmm, I'd suggest we send them and treat them like FAILED results.  But I
 guess the question is, who is expected to act based on the
 NEEDS_INSPECTION results?  For PASSED results, no action is needed by the
 maintainer.  For FAILED results, action is needed by the maintainer.  For
 NEEDS_INSPECTION results, I'm assuming action is needed by the maintain
 also?  Not just in resolving any issue (which is the case for FAILED
 results), but in identifying whether an issue exists.

 > Also, can we be sure that if depcheck does not produce output for some
 build, it
 > does mean that other builds were evaluated correctly?

 To rephrase ... because we couldn't close the deps loop, the concern is
 that we can't be sure we really did depsclosure?

 I'd hesitate to say we can't trust them ... because my sense is we'd
 bottleneck on depcheck results far too often.  My initial thought was we'd
 just treat these NEEDS_INSPECTION builds like others that FAILED depcheck.
 Unlike with FAILED results, our testing was not able to determine whether
 the builds are depsolvable, and they need manual inspection (note, this
 will need some docs for maintainers).

-- 
Ticket URL: <https://fedorahosted.org/autoqa/ticket/284#comment:9>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
_______________________________________________
autoqa-devel mailing list
[email protected]
https://fedorahosted.org/mailman/listinfo/autoqa-devel

Reply via email to