Reporting looks for a wrong ancestor

Bug #1101120 reported by Christophe Lyon
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Linaro Toolchain Build Automation
New
Undecided
Unassigned

Bug Description

While looking at benchmark results from
http://cbuild.validation.linaro.org/benchmarks/gcc-linaro-4.7%2bbzr115048~christophe-lyon~smin-umin-idiom/logs/armv7l-precise-cbuild446-tcpanda11-cortexa9hfr1/
I noticed that there is no *-diff.txt file.

It turns out that the reporter script is looking for a reference in gcc-linaro+bzr115047 which does not exist.

This information probably comes from
snapshots/gcc-linaro-4.7+bzr115048~christophe-lyon~smin-umin-idiom.txt
and maybe findancestor.find should actually check that the filename it returns is actually valid?

All other methods in findancestor seem to return '' in this case (find_via_variant, find_via_build and find_via_release).

I'd think that it should choose gcc-linaro-4.7+bzr115034 which does contain valid results.

Or, if we think that it shouldn't use that rev as reference, the user should get a warning about this, to help him debug such a situation.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.