Uploaded image for project: 'Fabric'
  1. Fabric
  2. FAB-16903

Intermittent test failure - etcdraft - should not disturb current running timer upon incorrect revalidation

    XMLWordPrintable

Details

    • (Please add steps to reproduce)

    Description

      16:46:39 {"level":"info","msg":"Created block [1], there are 0 blocks in flight","channel":"test-channel","node":1}
      16:46:39 {"level":"debug","msg":"Proposed block [1] to raft consensus","channel":"test-channel","node":1}
      16:46:39 {"level":"warn","msg":"slow fdatasync","channel":"test-channel","node":1,"took":"1.617046155s","expected-duration":"1s"}
      16:46:39 {"level":"info","msg":"Writing block [1] (Raft index: 3) to ledger","channel":"test-channel","node":1}
      16:46:39 {"level":"info","msg":"Raft node stopped","channel":"test-channel","node":1}
      16:46:39 {"level":"info","msg":"Stop serving requests","channel":"test-channel","node":1}
      16:46:39 {"level":"info","msg":"Periodic check is stopping.","channel":"test-channel","node":1}
      16:46:39 {"level":"debug","msg":"Quit proposing blocks, discarded 0 blocks in the queue","channel":"test-channel","node":1}
      16:46:39 
      16:46:39 ------------------------------
      16:46:39 • Failure [2.059 seconds]
      16:46:39 Chain
      16:46:39 /w/workspace/fabric-verify-unit-tests-x86_64/gopath/src/github.com/hyperledger/fabric/orderer/consensus/etcdraft/chain_test.go:78
      16:46:39   Single Raft node
      16:46:39   /w/workspace/fabric-verify-unit-tests-x86_64/gopath/src/github.com/hyperledger/fabric/orderer/consensus/etcdraft/chain_test.go:98
      16:46:39     when Raft leader is elected
      16:46:39     /w/workspace/fabric-verify-unit-tests-x86_64/gopath/src/github.com/hyperledger/fabric/orderer/consensus/etcdraft/chain_test.go:282
      16:46:39       Config updates
      16:46:39       /w/workspace/fabric-verify-unit-tests-x86_64/gopath/src/github.com/hyperledger/fabric/orderer/consensus/etcdraft/chain_test.go:473
      16:46:39         when a type A config update comes
      16:46:39         /w/workspace/fabric-verify-unit-tests-x86_64/gopath/src/github.com/hyperledger/fabric/orderer/consensus/etcdraft/chain_test.go:479
      16:46:39           for existing channel
      16:46:39           /w/workspace/fabric-verify-unit-tests-x86_64/gopath/src/github.com/hyperledger/fabric/orderer/consensus/etcdraft/chain_test.go:481
      16:46:39             with revalidation (i.e. incorrect config sequence)
      16:46:39             /w/workspace/fabric-verify-unit-tests-x86_64/gopath/src/github.com/hyperledger/fabric/orderer/consensus/etcdraft/chain_test.go:549
      16:46:39               should not disturb current running timer upon incorrect revalidation [It]
      16:46:39               /w/workspace/fabric-verify-unit-tests-x86_64/gopath/src/github.com/hyperledger/fabric/orderer/consensus/etcdraft/chain_test.go:572
      16:46:39 
      16:46:39               Timed out after 1.000s.
      16:46:39               Expected
      16:46:39                   <int>: 0
      16:46:39               to equal
      16:46:39                   <int>: 1
      16:46:39 
      16:46:39               /w/workspace/fabric-verify-unit-tests-x86_64/gopath/src/github.com/hyperledger/fabric/orderer/consensus/etcdraft/chain_test.go:589
      

      https://jenkins.hyperledger.org/job/fabric-verify-unit-tests-x86_64/15660/consoleFull

      eventually timeout is not lenient enough:

      16:46:39 {"level":"warn","msg":"slow fdatasync","channel":"test-channel","node":1,"took":"1.617046155s","expected-duration":"1s"}
      

      Attachments

        Activity

          People

            guoger Jay Guo
            guoger Jay Guo
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: