Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-75823

Concurrent modification exception on startup for coverage plugin

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Minor Minor
    • coverage-plugin, maven-plugin
    • Jenkins 2.504.3 (viewed on 2.504.2 too), with embedded Jetty on Linux RedHat 8.
      All plugins up to date. Coverage plugin 2.7.0.

      Sometimes, jobs with coverage analysis have their status, coverage values and execution date incorrectly loaded as shown in attached files.

      => job 212 was OK before restart but has problems after it.

      This happens randomly, not always on the same jobs when Jenkins restarts.

      When it occurs, Jenkins shows a warning on old value in jobs definition which reveals a ConcurrentModificationException. (also in attached files)

        1. job2 KO number 212.png
          job2 KO number 212.png
          1 kB
        2. job2 KO old data.png
          job2 KO old data.png
          14 kB
        3. job2 KO without coverage.png
          job2 KO without coverage.png
          3 kB
        4. job2 OK number 212.png
          job2 OK number 212.png
          2 kB
        5. job2 OK with coverage.png
          job2 OK with coverage.png
          5 kB

            Unassigned Unassigned
            jbreda Julien Bréda
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: