#1021
  • Created on
    2011-07-13 08:39
  • Reported by
    pveentjer
  • Status
    Duplicate
  • Priority
    High (2)
  • Assigned to
    -
  • Milestone
    2.0-M1
  • Plan Level
    -
  • Due Date
    -

Attachments

Jenkins Unreliable

From time to time Jenkins fails when it runs. This is not caused by the new code being checked in, but it could be some racy problem.

An example of this is the https://jenkins.typesafe.com/job/akka/68

Where Brendan checked in the durable mailboxes, but the test: akka.cluster.replication.transactionlog.writebehind.snapshot.ReplicationTransactionLogWriteBehindSnapshotMultiJvmNode2 fails. Something
that is not related to Brendan his functionality.

Later when Brendan adds documentation and checks it in at build https://jenkins.typesafe.com/job/akka/69 the build is a success.

So something non deterministic is going on.
User picture
  on 2011-07-13 08:41 *
By pveentjer
Description changed from From time to time Jenkins f... to From time to time Jenkins f...
User picture
  on 2011-07-13 08:41 *
By pveentjer
Description changed from From time to time Jenkins f... to From time to time Jenkins f...
User picture
  on 2011-08-11 14:36 *
By Jonas Bonér
Status changed from New to Duplicate
We have explicit tickets for the failing tests.
User picture
  on 2011-12-15 00:54 *
By viktorklang
Milestone changed from 2.0 to 2.0-M1
Updating tickets (#684, #883, #886, #995, #1017, #968, #969, #973, #1002, #1016, #1021, #1035, #1048, #1119, #1156, #1451, #231, #470, #595, #599, #639, #655, #687, #691, #692, #693, #724, #728, #729, #749, #751, #755, #765, #766, #767, #769, #770, #771, #772, #784, #785, #807)