Bug #7351
closed
Comparison of verification results for class "Validation on commits in Linux kernel Git repositories" does not work
Added by Evgeny Novikov almost 8 years ago.
Updated over 7 years ago.
Description
Here is a temporary link demonstrating this issue. You can notice that there are quite many changes in job files.
The reason is that one of attribute, namely "Commit", used for comparing isn't reported any more. Instead attribute "Name" is used.
As well you should report an error if you detect this inconsistency since now it looks like everything is well.
- Priority changed from Immediate to Urgent
This doesn't happen always. For instance, newly installed instances don't have such issues.
- Priority changed from Urgent to High
Let's consider this later.
- Priority changed from High to Immediate
We should fix this at last.
I didn't find any errors. Comparison is too long for jobs with full report trees. Check branch "fix_7351". I've optimized data extraction from DB for comparison. It should help for big jobs.
- Subject changed from Job comparison does not work to Comparison of lightweight verification results does not work
- Subject changed from Comparison of lightweight verification results does not work to Comparison of verification results for class "Validation on commits in Linux kernel Git repositories" does not work
- Description updated (diff)
- Due date set to 11/16/2016
- Status changed from New to Resolved
- % Done changed from 0 to 100
Fixed in branch "fix_7351".
- Status changed from Resolved to Closed
I merged the given branch to master in 2cddb29. In addition it brings some optimizations in comparing verification results.
Quite unpleasant news - for lightweight verification results transitions to/from safes aren't shown since just the total number of safes is known while their attributes aren't known by design.
Evgeny Novikov wrote:
Quite unpleasant news - for lightweight verification results transitions to/from safes aren't shown since just the total number of safes is known while their attributes aren't known by design.
That means we have to document that lightweight verification mode is just for users interested in bug finding.
Users who interested in experiments with verification engines and other components should not use this mode.
Also our reference runs should not use this mode.
Alexey Khoroshilov wrote:
Evgeny Novikov wrote:
Quite unpleasant news - for lightweight verification results transitions to/from safes aren't shown since just the total number of safes is known while their attributes aren't known by design.
That means we have to document that lightweight verification mode is just for users interested in bug finding.
Users who interested in experiments with verification engines and other components should not use this mode.
Also our reference runs should not use this mode.
Let's just keep this in mind, we have not enough time to develop good documentation yet. I didn't ever obtain lightweight verification results for the validation set but always do that when verifying all modules against all rules.
Also available in: Atom
PDF