https://forge.ispras.ru/https://forge.ispras.ru/favicon.ico?16490126692018-08-09T13:25:17ZOpen-Source ProjectsKlever - Bug #9200: Marks with zero similarity participate in 'incompatible' markshttps://forge.ispras.ru/issues/9200?journal_id=343282018-08-09T13:25:17ZEvgeny Novikovnovikov@ispras.ru
<ul><li><strong>Assignee</strong> set to <i>Vladimir Gratinskiy</i></li><li><strong>Priority</strong> changed from <i>Normal</i> to <i>Immediate</i></li></ul><p>There is another issue for the similarity limit. Here it is just required to avoid incompatible marks when similarities are 0. I suggest to still show these marks in various statistics by default as well as to show them after adopting a corresponding filter in views.</p> Klever - Bug #9200: Marks with zero similarity participate in 'incompatible' markshttps://forge.ispras.ru/issues/9200?journal_id=343912018-08-13T13:48:08ZVladimir Gratinskiygratinskiy@ispras.ru
<ul></ul><p>Can't find any action that makes 'incompatible' unsafes from marks with zero similarity.</p> Klever - Bug #9200: Marks with zero similarity participate in 'incompatible' markshttps://forge.ispras.ru/issues/9200?journal_id=343952018-08-13T14:45:32ZPavel Andrianovandrianov@ispras.ru
<ul></ul><p>What do you mean by 'action'? If you have one mark 'bug' for an error trace with 100% similarity and one mark 'false unsafe' with 0% similarity, the result is 'incompatible marks'. I suggest not to consider zero-similarity marks for incompatibility. Anyway, let them stay at various statistics.</p> Klever - Bug #9200: Marks with zero similarity participate in 'incompatible' markshttps://forge.ispras.ru/issues/9200?journal_id=344882018-08-21T11:37:16ZEvgeny Novikovnovikov@ispras.ru
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Resolved</i></li></ul><p>This was fixed in "bridge-1.1" as well.</p> Klever - Bug #9200: Marks with zero similarity participate in 'incompatible' markshttps://forge.ispras.ru/issues/9200?journal_id=344912018-08-21T11:42:56ZVladimir Gratinskiygratinskiy@ispras.ru
<ul></ul><p>Evgeny Novikov wrote:</p>
<blockquote>
<p>This was fixed in "bridge-1.1" as well.</p>
</blockquote>
<p>I'm not sure about that. Currently I'm trying to find what action (create mark/change mark/upload report, etc.) could lead to the bug.</p> Klever - Bug #9200: Marks with zero similarity participate in 'incompatible' markshttps://forge.ispras.ru/issues/9200?journal_id=344922018-08-21T11:46:19ZEvgeny Novikovnovikov@ispras.ru
<ul></ul><p>Vladimir Gratinskiy wrote:</p>
<blockquote>
<p>Evgeny Novikov wrote:</p>
<blockquote>
<p>This was fixed in "bridge-1.1" as well.</p>
</blockquote>
<p>I'm not sure about that. Currently I'm trying to find what action (create mark/change mark/upload report, etc.) could lead to the bug.</p>
</blockquote>
<p>It was enough to create 2 marks with different verdicts, one of which should have 0 similarity, another one >0 similarity. Other issues if so should be considered separately.</p> Klever - Bug #9200: Marks with zero similarity participate in 'incompatible' markshttps://forge.ispras.ru/issues/9200?journal_id=344942018-08-21T14:11:33ZPavel Andrianovandrianov@ispras.ru
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>Open</i></li></ul><p>The case is still present. We can not reproduce it, so here is one more link <a class="external" href="http://10.10.18.221:8998/reports/unsafe/5f10b811a211597f29b842cdb36cceca/">http://10.10.18.221:8998/reports/unsafe/5f10b811a211597f29b842cdb36cceca/</a>. Note, there are other similar unsafes (see 'incompatible marks' view).</p> Klever - Bug #9200: Marks with zero similarity participate in 'incompatible' markshttps://forge.ispras.ru/issues/9200?journal_id=345092018-08-23T11:37:26ZEvgeny Novikovnovikov@ispras.ru
<ul><li><strong>Status</strong> changed from <i>Open</i> to <i>Resolved</i></li></ul><p>It turned out that one needs to recalculate caches through the manager tools to get rid of the issue.</p> Klever - Bug #9200: Marks with zero similarity participate in 'incompatible' markshttps://forge.ispras.ru/issues/9200?journal_id=345122018-08-23T11:40:45ZEvgeny Novikovnovikov@ispras.ru
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>Closed</i></li></ul><p>As both automatic and manual tests passed, I merged the branch to master in <a class="changeset" title="Refactoring." href="https://forge.ispras.ru/projects/klever/repository/331/revisions/1c078402e0c0719b15ffd12b57e4d08e15c195f1">1c078402e</a>. Don't forget to recalculate caches for unsafe marks through the manager tools.</p>