You are viewing a plain text version of this content. The canonical link for it is here.
Posted to olio-dev@incubator.apache.org by "Shanti Subramanyam (JIRA)" <ji...@apache.org> on 2009/10/21 21:56:59 UTC

[jira] Commented: (OLIO-129) "Average Images in Tag Search Results" statistic in summary report often fails

    [ https://issues.apache.org/jira/browse/OLIO-129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768482#action_12768482 ] 

Shanti Subramanyam commented on OLIO-129:
-----------------------------------------

r828229 fixes this issue for rails. Relevant changes for UIDriver.java below :

@@ -1152,11 +1102,12 @@
             cnt = r.getOpsCountSteady("TagSearch");
             el[5] = new Element();
             el[5].description = "Average images on Tag Search Results";
-            el[5].target = "&gt;= 3.6";
+            //el[5].target = "&gt;= 3.6";
+            el[5].target = "&gt;= 0";
             if (cnt > 0) {
                 double avgImgs = tagSearchImages / (double) cnt;
                 el[5].result = String.format("%.2f", avgImgs);
-                if (avgImgs >= 3.6d) {
+                if (avgImgs >= 0) {
                     el[5].passed = Boolean.TRUE;
                 } else {
                     el[5].passed = Boolean.FALSE;



> "Average Images in Tag Search Results" statistic in summary report often fails
> ------------------------------------------------------------------------------
>
>                 Key: OLIO-129
>                 URL: https://issues.apache.org/jira/browse/OLIO-129
>             Project: Olio
>          Issue Type: Bug
>          Components: generic
>    Affects Versions: 0.1
>            Reporter: Shanti Subramanyam
>            Assignee: Shanti Subramanyam
>             Fix For: 0.2
>
>
> The number of entries returned by the TagSearch operation involves a complicated logic as tags do not scale linearly in the database. Consequently the requirement and test that #images be >= 3.6 doesn't always pass. It seems to hold true at higher scales but many runs at lower db scales fail this test. This causes the entire run to be marked as failed.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.