Depcheck will run on taskotron if changes from D136 are applied to taskotron
AbandonedPublic

Authored by jskladan on Jun 12 2014, 12:31 PM.

Details

Summary

These changes make depcheck runable in Taskotron.
Note that further changes are required, since squash_results needs to squash per-rpm results to per-builds updates before squashing the per-build results to per-update results.
It did not occur to me, at the beginning, that list of RPMs is not list of builds, so at the moment, depcheck can false-positive when one (or more) rpms from the build fails.

To be specific, let's have a build XYZ containing rpms XYZ.rpm XYZ_doc.rpm and XYZ_lib.rpm. The way it is currently (wrong) dealt with is, that squash_results gets list of per-rpm results, where the rpm name is converted to NVR.
This means that the overall build-outcome is not determined by aggregating all three rpms's results, but just on the XYZ.rpms outcome.

This needs to be dealt with, but the patch will not be a small one, and I will provide it once it is done.

Test Plan

unittests work, running through taskotron's runner works

Diff Detail

Repository
rDEPCK task-depcheck
Branch
feature/t187
Lint
No Linters Available
Unit
No Unit Test Coverage
jskladan retitled this revision from to Depcheck will run on taskotron if changes from D136 are applied to taskotron.Jun 12 2014, 12:31 PM
jskladan updated this object.
jskladan edited the test plan for this revision. (Show Details)
jskladan added reviewers: tflink, kparal, mkrizek.
jskladan abandoned this revision.Jun 12 2014, 12:52 PM