[tests] murano coverage job can lead to false positives because it checkouts stale code

Bug #1610734 reported by Kirill Zaitsev on 2016-08-07
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Murano
Medium
Unassigned

Bug Description

See this commit as an example. https://review.openstack.org/#/c/352088/2 http://logs.openstack.org/88/352088/2/check/murano-coverage-db-ubuntu-xenial/bf7db82/

Since the job does checkout — it can checkout stale code (the one that differs from up-to-date master). In the current master we could have increased the coverage, and the job would compare the result with stale coverage results. Thus the job will give false-negatives on legitimate commits.

We could force the job to cherry-pick the commit in question on top of master (or merge, or rebase) in order to get correct results

Changed in murano:
importance: High → Medium
Changed in murano:
milestone: newton-3 → newton-rc1
Changed in murano:
milestone: newton-rc1 → newton-rc2
Changed in murano:
milestone: newton-rc2 → ocata-1
Changed in murano:
milestone: 3.1.0 → pike-2
Changed in murano:
milestone: pike-2 → pike-rc1
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers