14 Replies Latest reply: Aug 7, 2012 7:38 AM by stevenlemay RSS

After upgrading to Prevent Platform 6.0.1 all issues report as "Resolved"

stevenlemay Contributor
Currently Being Moderated

Just finished the first static analysis run using Prevent 6.0.1.  Once I committed to the newly installed Integrity Manager all the issues were marked as "Resolved" destroying the status of all of the actual issues.  No "New", "Fixed" or any other status was valid.  What went wrong?  The analysis console output looked as expected and the commit succeeded with no obvious issues.  Any advice?  This has really taken down our whole triage and fix system...

  • Re: After upgrading to Prevent Platform 6.0.1 all issues report as "Resolved"
    vspurlin Genius
    Currently Being Moderated

    Hi Steve - I see that you've also opened a support case for this problem, so I'll work with you on resolving it through the case. My first impression is that the commit hadn't finished, and you may see different results when it's done. But we'll find out when we follow up through the support case - Vaughn

    • Re: After upgrading to Prevent Platform 6.0.1 all issues report as "Resolved"
      stevenlemay Contributor
      Currently Being Moderated

      Although the commit progress bars all show complete for the past hour, the CPU utilization suggests that the commit process is still in progress.  There are significant changes to the results between SA 5.51 and SA 6.0.1 and hopefully its taking a very usual amount of extra time to commit the results to the database for IM.  While this is in progress the latest scan results show that all issues are 100% resolved, which causes a great deal of concern for our routine users.  As I write this the commit process is hopefully proceeding normally (just very, very long time compared to previous 5.5.1 commits).

      • Re: After upgrading to Prevent Platform 6.0.1 all issues report as "Resolved"
        Asya Kamsky Coverity Ninja
        Currently Being Moderated

        The commit isn't complete until it prints

         

        New snapshot ID XXXX added.

        • Re: After upgrading to Prevent Platform 6.0.1 all issues report as "Resolved"
          stevenlemay Contributor
          Currently Being Moderated

          The previous commits of the same source base and analysis typically committed in under 15 minutes, and maybe this will improve after the first SA 6.0.1 snapshot completes.  Misleadingly, the console status (shown below) is presented and becomes static after 10 or so minutes after executing the commit.  The spinner no longer appears, and all appears to be "locked up".  Which is everyone's fear when deploying new software. Previously, once reaching this point the commit would complete.  The CIM log is growing larger by the second, currently after 3 hours (and going) entries are repeated (shown below). It appears the transaction time shown in the log is also increasing from ~100 ms to ~1800ms each.  If this log represents one transaction for each possible issue - this process may take 8-10 hours (or more) to complete.  (I'm uncertain what the log actually indicates).  This is a far cry from the previous 10-15 minute commit time with Prevent 5.5.1.  Hopefully, this is a one time price to be paid post conversion.  On a positive note, the analysis time dropped from ~5.5 hours (SA5.5.1) to ~3.5(SA6.0.1) hours with the same configuration and options (8 concurrent jobs).

           

          2012-04-19 13:41:42.111  INFO MethodExecutionAdvice,pool-20-thread-1:76 - Executed: HibernateStreamDefectDao.getAllForMergedDefectAndTriageStores time(ms): 122.253

          2012-04-19 13:41:42.218  INFO MethodExecutionAdvice,pool-20-thread-1:76 - Executed: HibernateStreamDefectDao.getAllForMergedDefectAndTriageStores time(ms): 106.444

          2012-04-19 13:41:42.326  INFO MethodExecutionAdvice,pool-20-thread-1:76 - Executed: HibernateDefectTriageDao.getByTriageStoreAndMergedDefect time(ms): 107.77

          2012-04-19 13:41:42.461  INFO MethodExecutionAdvice,pool-20-thread-1:76 - Executed: HibernateStreamDefectDao.getAllForMergedDefectAndTriageStores time(ms): 124.330

          2012-04-19 13:41:42.568  INFO MethodExecutionAdvice,pool-20-thread-1:76 - Executed: HibernateStreamDefectDao.getAllForMergedDefectAndTriageStores time(ms): 105.882

          2012-04-19 13:41:42.708  INFO MethodExecutionAdvice,pool-20-thread-1:76 - Executed: HibernateStreamDefectDao.getAllForMergedDefectAndTriageStores time(ms): 121.933

          2012-04-19 13:41:42.816  INFO MethodExecutionAdvice,pool-20-thread-1:76 - Executed: HibernateStreamDefectDao.getAllForMergedDefectAndTriageStores time(ms): 106.991

          2012-04-19 13:41:42.923  INFO MethodExecutionAdvice,pool-20-thread-1:76 - Executed: HibernateDefectTriageDao.getByTriageStoreAndMergedDefect time(ms): 106.657

          2012-04-19 13:41:43.058  INFO MethodExecutionAdvice,pool-20-thread-1:76 - Executed: HibernateStreamDefectDao.getAllForMergedDefectAndTriageStores time(ms): 124.720

          2012-04-19 13:41:43.166  INFO MethodExecutionAdvice,pool-20-thread-1:76 - Executed: HibernateStreamDefectDao.getAllForMergedDefectAndTriageStores time(ms): 107.210

          2012-04-19 13:41:43.275  INFO MethodExecutionAdvice,pool-20-thread-1:76 - Executed: HibernateDefectTriageDao.getByTriageStoreAndMergedDefect time(ms): 106.939

          2012-04-19 13:41:43.404  INFO MethodExecutionAdvice,pool-20-thread-1:76 - Executed: HibernateStreamDefectDao.getAllForMergedDefectAndTriageStores time(ms): 124.104

          2

          ...

          ... [thousands of entries deleted[

          ...

          2012-04-19 16:33:55.270  INFO MethodExecutionAdvice,pool-20-thread-1:76 - Executed: HibernateStreamDefectDao.getAllForMergedDefectAndTriageStores time(ms): 1737.376

          2012-04-19 16:33:56.793  INFO MethodExecutionAdvice,pool-20-thread-1:76 - Executed: HibernateStreamDefectDao.getAllForMergedDefectAndTriageStores time(ms): 1522.8

          2012-04-19 16:33:58.552  INFO MethodExecutionAdvice,pool-20-thread-1:76 - Executed: HibernateStreamDefectDao.getAllForMergedDefectAndTriageStores time(ms): 1740.74

          2012-04-19 16:34:00.095  INFO MethodExecutionAdvice,pool-20-thread-1:76 - Executed: HibernateStreamDefectDao.getAllForMergedDefectAndTriageStores time(ms): 1540.706

          2012-04-19 16:34:01.917  INFO MethodExecutionAdvice,pool-20-thread-1:76 - Executed: HibernateStreamDefectDao.getAllForMergedDefectAndTriageStores time(ms): 1803.413

          2012-04-19 16:34:03.454  INFO MethodExecutionAdvice,pool-20-thread-1:76 - Executed: HibernateStreamDefectDao.getAllForMergedDefectAndTriageStores time(ms): 1536.696

          2012-04-19 16:34:05.213  INFO MethodExecutionAdvice,pool-20-thread-1:76 - Executed: HibernateStreamDefectDao.getAllForMergedDefectAndTriageStores time(ms): 1738.668

           

          ========  CONSOLE OUTPUT PROVES TO NOT BE VERY USEFUL IN THIS CASE ===============

           

          D:\Coverity>commit.bat

          Coverity Defect Commit Client version 6.0.1 on Windows Server 2008 R2 Server Sta

          ndard (full installation), 64-bit, Service Pack 1 (build 7601)

          Internal version numbers: 1.5222:3042, 20120412041511UTC, p-berkeley-push-11376.

          367

           

           

          Connecting to server localhost:9090

          2012-04-19 20:28:01 UTC - Committing 8642 file descriptions...

          |0----------25-----------50----------75---------100|

          ****************************************************

          2012-04-19 20:29:05 UTC - Committing cross-references for 8642 files...

          |0----------25-----------50----------75---------100|

          ****************************************************

          2012-04-19 20:32:45 UTC - Committing 239421 functions...

          |0----------25-----------50----------75---------100|

          ****************************************************

          2012-04-19 20:34:46 UTC - Committing 14798 defect occurrences...

          |0----------25-----------50----------75---------100|

          ****************************************************

  • Re: After upgrading to Prevent Platform 6.0.1 all issues report as "Resolved"
    matspi Genius
    Currently Being Moderated

    Same here.

    When the commit starts, the new snapshot number is already visible in "History" -> "Snapshots".

     

    All defects are marked as "Fixed". Also "Source" -> "Defects" shows them as "Fixed".

     

    No transition to fixed can be seen in the "History" below the triage panel.

    With commits taking about one hour this leads to quite some confusion.

     

    Matthias

  • Re: After upgrading to Prevent Platform 6.0.1 all issues report as "Resolved"
    matspi Genius
    Currently Being Moderated

    The support keeps on telling me that the commit procedure has not changed between 5.5.3 and 6.0.1.

    Thus this issue also exists with 5.5.3 and is "only" a performance problem.

     

    I have tried again and again and I could NOT see the problem with 5.5.3. With 5.5.3, during a commit, the defects are still "Outstanding" and not "Fixed".

     

    Can anyone comfirm my observations?

     

    Thanks,

    Matthias

  • Re: After upgrading to Prevent Platform 6.0.1 all issues report as "Resolved"
    stevenlemay Contributor
    Currently Being Moderated

    This issue is to be corrected in the next Prevent release.  It is related to a bug in the commit process when assigning owners automatically to issues.

    • Re: After upgrading to Prevent Platform 6.0.1 all issues report as "Resolved"
      stevenlemay Contributor
      Currently Being Moderated

      With Coverity 6.0.2 the commit now takes about 30 minute.  A vast improvement over 6.0.1.  Now we just need to address the 25% false positive rate when aggressiveness set to high and using the plug-in with QNX Momentics (Eclipse variant),  That would be awesome.

       

      Analysis summary report:

      ------------------------

      Files analyzed                  : 7582

      Total LoC input to cov-analyze  : 2931131

      Functions analyzed              : 246770

      Classes/structs analyzed        : 38631

      Paths analyzed                  : 20831650

      Time taken by Coverity analysis : 04:29:08

      Defect occurrences found        : 13509 Total

                                           29 ARRAY_VS_SINGLETON

                                            1 ASSERT_SIDE_EFFECT

                                            1 BAD_FREE

                                           93 BAD_SIZEOF

                                            4 BUFFER_SIZE

                                            8 BUFFER_SIZE_WARNING

                                         1125 CHECKED_RETURN

                                          742 CONSTANT_EXPRESSION_RESULT

                                           14 COPY_PASTE_ERROR

                                            3 CTOR_DTOR_LEAK

                                          112 DEADCODE

                                           22 DIVIDE_BY_ZERO

                                          324 FORWARD_NULL

                                         1073 HFA

                                            2 INCOMPATIBLE_CAST

                                           22 INFINITE_LOOP

                                          386 INTEGER_OVERFLOW

                                            5 INVALIDATE_ITERATOR

                                            1 LOCK

                                            7 MISMATCHED_ITERATOR

                                           74 MISSING_BREAK

                                            2 MISSING_LOCK

                                          109 MIXED_ENUMS

                                           10 NEGATIVE_RETURNS

                                          326 NO_EFFECT

                                         2341 NULL_RETURNS

                                           16 OVERFLOW_BEFORE_WIDEN

                                           92 OVERRUN

                                            6 OVERRUN_DYNAMIC

                                          191 OVERRUN_STATIC

                                          137 PASS_BY_VALUE

                                            2 PW.BRANCH_PAST_INITIALIZATION

                                            3 PW.CONVERSION_TO_POINTER_LOSES_BITS

                                          106 PW.DECLARED_BUT_NOT_REFERENCED

                                           23 PW.INCLUDE_RECURSION

                                            9 PW.INCOMPATIBLE_ASSIGNMENT_OPERANDS

                                            4 PW.INCOMPATIBLE_PARAM

                                           80 PW.MIXED_ENUM_TYPE

                                          101 PW.NESTED_COMMENT

                                          110 PW.NON_CONST_PRINTF_FORMAT_STRING

                                           32 PW.NO_CTOR_BUT_CONST_OR_REF_MEMBER

                                           27 PW.PARAMETER_HIDDEN

                                            6 PW.PARAM_SET_BUT_NOT_USED

                                            1 PW.POINTER_OUTSIDE_BASE_OBJECT

                                          259 PW.SET_BUT_NOT_USED

                                            3 PW.SWITCH_SELECTOR_EXPR_IS_CONSTANT

                                          402 RESOURCE_LEAK

                                           49 REVERSE_INULL

                                            1 REVERSE_NEGATIVE

                                            6 RW.REGISTER_USED_TWICE

                                            7 RW.ROUTINE_NOT_EMITTED

                                            6 RW.STATEMENT_EXPRESSION_IN_FUNCTION_ONLY

                                          183 RW.UNDEFINED_IDENTIFIER

                                          139 SECURE_CODING

                                            1 SECURE_TEMP

                                           31 SIZEOF_MISMATCH

                                           48 STACK_USE

                                            5 STRAY_SEMICOLON

                                            9 STRING_NULL

                                            4 STRING_OVERFLOW

                                            4 STRING_SIZE

                                          185 TAINTED_SCALAR

                                            3 TAINTED_STRING

                                           98 TAINTED_STRING_WARNING

                                            4 TOCTOU

                                         3416 UNINIT

                                          756 UNINIT_CTOR

                                            4 UNREACHABLE

                                           71 UNUSED_VALUE

                                            7 USE_AFTER_FREE

                                            1 VARARGS

                                            1 VIRTUAL_DTOR

                                           24 WRAPPER_ESCAPE

       

       

      Exceeded path limit of 5000 paths in 0.62% of functions (normally up to 5% of functions encounter this limitation)

      Coverity Defect Commit Client version 6.0.2 on Windows Server 2008 R2 Server Standard (full installation), 64-bit, Servi

      ce Pack 1 (build 7601)

      Internal version numbers: 1.5358:43036, 20120608203551UTC, p-bplus-push-11376.369.138

       

       

      Connecting to server localhost:9090

      2012-08-07 03:55:06 UTC - Committing 8948 file descriptions...

      |0----------25-----------50----------75---------100|

      ****************************************************

      2012-08-07 03:57:11 UTC - Committing 238 source files...

      |0----------25-----------50----------75---------100|

      ****************************************************

      2012-08-07 03:57:19 UTC - Committing cross-references for 8948 files...

      |0----------25-----------50----------75---------100|

      ****************************************************

      2012-08-07 04:01:17 UTC - Committing 246770 functions...

      |0----------25-----------50----------75---------100|

      ****************************************************

      2012-08-07 04:04:30 UTC - Committing 13509 defect occurrences...

      |0----------25-----------50----------75---------100|

      ****************************************************

      2012-08-07 04:25:51 UTC - Committing 4 output files...

      |0----------25-----------50----------75---------100|

      ****************************************************

      New snapshot ID 10072 added.

      Elapsed time: 00:30:52

More Like This

  • Retrieving data ...

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points