Details

    • Bug
    • Status: Resolved
    • Blocker
    • Resolution: Fixed
    • None
    • 2.0.0-beta-2, 2.0.0
    • test
    • None

    Attachments

      Issue Links

        There are no Sub-Tasks for this issue.

        Activity

          elserj Josh Elser added a comment -

          TestNamespacesInstanceResource, TestReplicaWithCluster, TestReplicationAdmin, and TestRegionServerHostname are failing for me locally as of alpha-4 rc0

          elserj Josh Elser added a comment - TestNamespacesInstanceResource, TestReplicaWithCluster, TestReplicationAdmin, and TestRegionServerHostname are failing for me locally as of alpha-4 rc0
          stack Michael Stack added a comment -

          Thanks elserj I'm starting to go through them...

          stack Michael Stack added a comment - Thanks elserj I'm starting to go through them...
          elserj Josh Elser added a comment -

          Looking at TestRegionServerHostname. Give me a shout if you've already fixed some locally, stack.

          elserj Josh Elser added a comment - Looking at TestRegionServerHostname. Give me a shout if you've already fixed some locally, stack .
          stack Michael Stack added a comment -

          Tried a run on a physical machine.

          Total time: 07:52 h

          Tests run: 2450, Failures: 53, Errors: 66, Skipped: 36 ... loads of spew here too with tests getting killed. Maybe my host is sick (though that'd make two in this cluster...)

          stack Michael Stack added a comment - Tried a run on a physical machine. Total time: 07:52 h Tests run: 2450, Failures: 53, Errors: 66, Skipped: 36 ... loads of spew here too with tests getting killed. Maybe my host is sick (though that'd make two in this cluster...)
          stack Michael Stack added a comment -

          New run. 7.21h. Tests run: 2665, Failures: 24, Errors: 65, Skipped: 42 .. which is a good few more tests than ran above. Nightly says ' Tests run: 2039, Failures: 1, Errors: 0, Skipped: 24, Flakes: 2' for second part (looking at a few ... they are all just over 2k for second part of hbase-server).

          stack Michael Stack added a comment - New run. 7.21h. Tests run: 2665, Failures: 24, Errors: 65, Skipped: 42 .. which is a good few more tests than ran above. Nightly says ' Tests run: 2039, Failures: 1, Errors: 0, Skipped: 24, Flakes: 2' for second part (looking at a few ... they are all just over 2k for second part of hbase-server).
          stack Michael Stack added a comment -

          7.23h Tests run: 2742, Failures: 31, Errors: 54, Skipped: 44 ... Tests run varies. Nightly time is less, 4h 47min.

          stack Michael Stack added a comment - 7.23h Tests run: 2742, Failures: 31, Errors: 54, Skipped: 44 ... Tests run varies. Nightly time is less, 4h 47min.
          busbey Sean Busbey added a comment -

          Is the goal to also have those currently flagged as flaky pass?

          busbey Sean Busbey added a comment - Is the goal to also have those currently flagged as flaky pass?
          busbey Sean Busbey added a comment -

          And is it fine if things pass because we reduce concurrency? or do you want these working under duress?

          busbey Sean Busbey added a comment - And is it fine if things pass because we reduce concurrency? or do you want these working under duress?
          stack Michael Stack added a comment -

          Was thinking flakies should pass and concurrency shouldn't have an effect on how many tests pass or fail. Thats the hope.

          stack Michael Stack added a comment - Was thinking flakies should pass and concurrency shouldn't have an effect on how many tests pass or fail. Thats the hope.
          chia7712 Chia-Ping Tsai added a comment -

          stack Just curious. Should we move all issues about the flaky fix to this parent issue? Or this issue is a caveat for 2.0 release?

          chia7712 Chia-Ping Tsai added a comment - stack Just curious. Should we move all issues about the flaky fix to this parent issue? Or this issue is a caveat for 2.0 release?
          stack Michael Stack added a comment -

          Did you chia7712 suggested and added failing tests as subtasks to here.

          stack Michael Stack added a comment - Did you chia7712 suggested and added failing tests as subtasks to here.
          stack Michael Stack added a comment -

          We got a pass on a nightly for hadoop2. Failed in hadoop3: https://builds.apache.org/view/H-L/view/HBase/job/HBase%20Nightly/job/branch-2/

          stack Michael Stack added a comment - We got a pass on a nightly for hadoop2. Failed in hadoop3:  https://builds.apache.org/view/H-L/view/HBase/job/HBase%20Nightly/job/branch-2/
          hudson Hudson added a comment -

          FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #4511 (See https://builds.apache.org/job/HBase-Trunk_matrix/4511/)
          HBASE-19147 TestCacheOnWrite Times Out (stack: rev 3622bb0333ea1b7c05fd47e5e0fee61b82f08109)

          • (edit) hbase-server/src/test/java/org/apache/hadoop/hbase/io/hfile/TestCacheOnWrite.java
          hudson Hudson added a comment - FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #4511 (See https://builds.apache.org/job/HBase-Trunk_matrix/4511/ ) HBASE-19147 TestCacheOnWrite Times Out (stack: rev 3622bb0333ea1b7c05fd47e5e0fee61b82f08109) (edit) hbase-server/src/test/java/org/apache/hadoop/hbase/io/hfile/TestCacheOnWrite.java
          zhangduo Duo Zhang added a comment -

          Do we need to go over the tests again to see the ignore ones?

          Thanks.

          zhangduo Duo Zhang added a comment - Do we need to go over the tests again to see the ignore ones? Thanks.
          stack Michael Stack added a comment -

          Do we need to go over the tests again to see the ignore ones?

          We could. I made one pass flagging tests that no longer made sense in AMv2 context and fixing others. Could do another pass but I think we in pretty good shape after we nail the current failing set (almost there).

          stack Michael Stack added a comment - Do we need to go over the tests again to see the ignore ones? We could. I made one pass flagging tests that no longer made sense in AMv2 context and fixing others. Could do another pass but I think we in pretty good shape after we nail the current failing set (almost there).
          zhangduo Duo Zhang added a comment -

          Do we want to fix TestAssignmentManagerMetrics? It is stuck when modifying table with a coprocessor jar which does not exist.

          zhangduo Duo Zhang added a comment - Do we want to fix TestAssignmentManagerMetrics? It is stuck when modifying table with a coprocessor jar which does not exist.
          stack Michael Stack added a comment -

          Let me have a go at it.... trying to figure the Merge Region failure. Have an idea...

          stack Michael Stack added a comment - Let me have a go at it.... trying to figure the Merge Region failure. Have an idea...
          stack Michael Stack added a comment -

          Resolving umbrella issue. Subtasks have been done.

          nightly branch-2.0 passed for the first time last night. This means all tests passed running on hadoop2 and then all tests passed again on top of hadoop3. It has been threatening for a while (yesterday two nightlies passed all unit tests but failed because there were some findbugs unresolved).

          stack Michael Stack added a comment - Resolving umbrella issue. Subtasks have been done. nightly branch-2.0 passed for the first time last night. This means all tests passed running on hadoop2 and then all tests passed again on top of hadoop3. It has been threatening for a while (yesterday two nightlies passed all unit tests but failed because there were some findbugs unresolved).

          People

            stack Michael Stack
            stack Michael Stack
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: