java.lang.AssertionError: unexpected pending count, expected 1, got 3

JIRA | Kevin Normoyle | 2 years ago
tip
Click on the to mark the solution that helps you, Samebug will learn from it.
As a community member, you’ll be rewarded for you help.
  1. 0

    Maybe that's the first step, is to see if all NOPASS r tests have a jira I assume they don't This goes to my question of gauging doneness. i think test writers know that certain features aren't in yet, and maybe a NOPASS test exposes that, but there's not an expectation that test writers are somehow riding herd on project management..i.e. responsible for documenting all "work not yet done' I filed a jira on this I think it overlaps with an existing jira that gets the same It's reasonable to say that the JIRA next step, should be to modify the test to not be intermittent ------------------------------ It should have a ticket whether or not it's intermittent. Please fill in the test case field. On Mar 6, 2015 5:10 PM, "Kevin" <kevin@0xdata.com> wrote: there are numerous GLM tests that get these intermittent failures, that I changed to NOPASS, and they're being changed from NOPASS, with no underlying change to GLM, so they just fail again intermittently, and I change them back to NOPASS. Maybe the problem is there's no jira filed on these? If the test is intermittent, it probably needs modification to only run the case that fails, multiple times. Or with a fixed seed that matches the failure. Then it's not intermittent and can be a jira http://172.16.2.161:8080/job/h2o_master_DEV_runit_small/7018/artifact/h2o-r/tests/results/java_3_0.out.txt http://172.16.2.161:8080/job/h2o_master_DEV_runit_small/7018/console True fail list: runit_demo_exec2.R http://172.16.2.161:8080/job/h2o_master_DEV_runit_small/7018/artifact/h2o-r/tests/results/java_3_0.out.txt barrier onExCompletion for hex.glm.GLM$1@76a4120d java.lang.AssertionError: unexpected pending count, expected 1, got 3 at hex.glm.GLM$GLMLambdaTask$LineSearchIteration.callback(GLM.java:529) at hex.glm.GLM$GLMLambdaTask$LineSearchIteration.callback(GLM.java:524) at water.H2O$H2OCallback.onCompletion(H2O.java:641) at jsr166y.CountedCompleter.tryComplete(CountedCompleter.java:386) at water.MRTask.compute2(MRTask.java:439) at water.H2O$H2OCountedCompleter.compute(H2O.java:583) at jsr166y.CountedCompleter.exec(CountedCompleter.java:429) at jsr166y.ForkJoinTask.doExec(ForkJoinTask.java:263) at jsr166y.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:974) at jsr166y.ForkJoinPool.runWorker(ForkJoinPool.java:1477) at jsr166y.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:104)

    JIRA | 2 years ago | Kevin Normoyle
    java.lang.AssertionError: unexpected pending count, expected 1, got 3
  2. 0

    Maybe that's the first step, is to see if all NOPASS r tests have a jira I assume they don't This goes to my question of gauging doneness. i think test writers know that certain features aren't in yet, and maybe a NOPASS test exposes that, but there's not an expectation that test writers are somehow riding herd on project management..i.e. responsible for documenting all "work not yet done' I filed a jira on this I think it overlaps with an existing jira that gets the same It's reasonable to say that the JIRA next step, should be to modify the test to not be intermittent ------------------------------ It should have a ticket whether or not it's intermittent. Please fill in the test case field. On Mar 6, 2015 5:10 PM, "Kevin" <kevin@0xdata.com> wrote: there are numerous GLM tests that get these intermittent failures, that I changed to NOPASS, and they're being changed from NOPASS, with no underlying change to GLM, so they just fail again intermittently, and I change them back to NOPASS. Maybe the problem is there's no jira filed on these? If the test is intermittent, it probably needs modification to only run the case that fails, multiple times. Or with a fixed seed that matches the failure. Then it's not intermittent and can be a jira http://172.16.2.161:8080/job/h2o_master_DEV_runit_small/7018/artifact/h2o-r/tests/results/java_3_0.out.txt http://172.16.2.161:8080/job/h2o_master_DEV_runit_small/7018/console True fail list: runit_demo_exec2.R http://172.16.2.161:8080/job/h2o_master_DEV_runit_small/7018/artifact/h2o-r/tests/results/java_3_0.out.txt barrier onExCompletion for hex.glm.GLM$1@76a4120d java.lang.AssertionError: unexpected pending count, expected 1, got 3 at hex.glm.GLM$GLMLambdaTask$LineSearchIteration.callback(GLM.java:529) at hex.glm.GLM$GLMLambdaTask$LineSearchIteration.callback(GLM.java:524) at water.H2O$H2OCallback.onCompletion(H2O.java:641) at jsr166y.CountedCompleter.tryComplete(CountedCompleter.java:386) at water.MRTask.compute2(MRTask.java:439) at water.H2O$H2OCountedCompleter.compute(H2O.java:583) at jsr166y.CountedCompleter.exec(CountedCompleter.java:429) at jsr166y.ForkJoinTask.doExec(ForkJoinTask.java:263) at jsr166y.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:974) at jsr166y.ForkJoinPool.runWorker(ForkJoinPool.java:1477) at jsr166y.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:104)

    JIRA | 2 years ago | Kevin Normoyle
    java.lang.AssertionError: unexpected pending count, expected 1, got 3
  3. Speed up your debug routine!

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. java.lang.AssertionError

      unexpected pending count, expected 1, got 3

      at hex.glm.GLM$GLMLambdaTask$LineSearchIteration.callback()
    2. hex.glm
      GLM$GLMLambdaTask$LineSearchIteration.callback
      1. hex.glm.GLM$GLMLambdaTask$LineSearchIteration.callback(GLM.java:529)
      2. hex.glm.GLM$GLMLambdaTask$LineSearchIteration.callback(GLM.java:524)
      2 frames
    3. water
      H2O$H2OCallback.onCompletion
      1. water.H2O$H2OCallback.onCompletion(H2O.java:641)
      1 frame
    4. jsr166y
      CountedCompleter.tryComplete
      1. jsr166y.CountedCompleter.tryComplete(CountedCompleter.java:386)
      1 frame
    5. water
      H2O$H2OCountedCompleter.compute
      1. water.MRTask.compute2(MRTask.java:439)
      2. water.H2O$H2OCountedCompleter.compute(H2O.java:583)
      2 frames
    6. jsr166y
      ForkJoinWorkerThread.run
      1. jsr166y.CountedCompleter.exec(CountedCompleter.java:429)
      2. jsr166y.ForkJoinTask.doExec(ForkJoinTask.java:263)
      3. jsr166y.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:974)
      4. jsr166y.ForkJoinPool.runWorker(ForkJoinPool.java:1477)
      5. jsr166y.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:104)
      5 frames