Uploaded image for project: 'Clover'
  1. Clover
  2. CLOV-1151

Clover fails to find coverage snapshot files when IBM JRE is used

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Low Low
    • 3.1.8
    • 3.1.7
    • Instrumentation
    • None

      Problem: it seems that IBM JRE implementation differs from Oracle JRE in such way that Object.hashCode() can return a negative value. As a consequence, file name suffix generated for coverage snapshot and test slice snapshot may be composed not only of '0-9a-z_' characters, but also have minus "-" sign in it.

      As a result such file name does not match regular expression used for searching of coverage files and coverage is not read.

      Workaround: rename coverage snapshot file(s) and remove "-" character.

            [CLOV-1151] Clover fails to find coverage snapshot files when IBM JRE is used

            Owen made changes -
            Workflow Original: New Clover Workflow [ 897653 ] New: New Clover Workflow - Restricted [ 1474328 ]
            Piotr Swiecicki made changes -
            Workflow Original: Clover Workflow [ 895435 ] New: New Clover Workflow [ 897653 ]
            Piotr Swiecicki made changes -
            Workflow Original: reviewflow [ 407819 ] New: Clover Workflow [ 895435 ]
            Marek Parfianowicz made changes -
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Marek Parfianowicz made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: To be reviewed [ 10026 ] New: Resolved [ 5 ]
            Marek Parfianowicz made changes -
            Sprint New: Version 3.1.8 [ 99 ]
            Marek Parfianowicz made changes -
            Status Original: Implemented [ 10025 ] New: To be reviewed [ 10026 ]
            Marek Parfianowicz made changes -
            Status Original: Open [ 1 ] New: Implemented [ 10025 ]
            Marek Parfianowicz created issue -

              mparfianowicz Marek Parfianowicz
              mparfianowicz Marek Parfianowicz
              Affected customers:
              0 This affects my team
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Estimated:
                  Original Estimate - 4h
                  4h
                  Remaining:
                  Remaining Estimate - 4h
                  4h
                  Logged:
                  Time Spent - Not Specified
                  Not Specified