• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • multijob-plugin
    • None
    • Jenkins weekly 2.288
      Multijob plugin 1.36
      CentOS 7

      Noticed this in our Jenkins log:

      2021-04-13 19:45:20.623+0000 [id=387080]        WARNING c.t.j.p.m.QuietPeriodCalculator#calculate: Error calculating quiet time for index 1 and quietPeriodGroovy []: null; returning 0
      java.lang.NullPointerException
              at com.tikal.jenkins.plugins.multijob.QuietPeriodCalculator.calculateOrThrow(QuietPeriodCalculator.java:52)
              at com.tikal.jenkins.plugins.multijob.QuietPeriodCalculator.calculate(QuietPeriodCalculator.java:34)
              at com.tikal.jenkins.plugins.multijob.SubTask.generateFuture(SubTask.java:74)
              at com.tikal.jenkins.plugins.multijob.MultiJobBuilder$SubJobWorker.call(MultiJobBuilder.java:515)
              at java.util.concurrent.FutureTask.run(FutureTask.java:266)
              at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
              at java.util.concurrent.FutureTask.run(FutureTask.java:266)
              at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
              at java.lang.Thread.run(Thread.java:748) 

      Not sure currently about the circumstances or impact, so not setting a priority, but an unhandled NULL dereference is not right anyway

          [JENKINS-65357] NPE in multijob-plugin

          Paul Brightly added a comment -

          Any idea what's causing this or how to work around it?  I see this all the time.

          Paul Brightly added a comment - Any idea what's causing this or how to work around it?  I see this all the time.

          Paul Brightly added a comment -

          I later realized the setting in multi-job config.. We never paid attention to it, and all our jobs were blank. I put a 0 in there and it avoids the problem.

          Paul Brightly added a comment - I later realized the setting in multi-job config.. We never paid attention to it, and all our jobs were blank. I put a 0 in there and it avoids the problem.

            Unassigned Unassigned
            jimklimov Jim Klimov
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: