You can rebuild the commit and force push this results in the job being queued on different machines. It ends helping the test pass.
-Ali On Fri, Apr 2, 2021 at 9:09 AM Jonathan Ellis <jbel...@gmail.com> wrote: > Is there a legit regression causing elevated failures? > > On Fri, Apr 2, 2021 at 10:30 AM Enrico Olivelli <eolive...@gmail.com> > wrote: > > > Hello, > > today I see these tests (below) that are failing most of the PR > > validation jobs that I am tracking. > > it it literally the whole day that I am rerunning CI jobs, without > success > > > > What can we do ? Perhaps I am too pessimistic but it looks like the > > whole PR validation pipeline is stuck. > > > > Enrico > > > > Error: > > > testOrderingWithConsumerListener(org.apache.pulsar.client.api.KeySharedSubscriptionTest) > > Time elapsed: 1.912 s <<< FAILURE! > > 925 > > java.lang.AssertionError: expected [true] but found [false] > > > > Error: > > > testBrokerConnectionStats(org.apache.pulsar.broker.service.PersistentTopicE2ETest) > > Time elapsed: 0.275 s <<< FAILURE! > > java.lang.AssertionError: expected [0] but found [1] > > > > Error: > > > testRedeliveryFailOverConsumer(org.apache.pulsar.broker.service.persistent.SimpleProducerConsumerTestStreamingDispatcherTest) > > Time elapsed: 2.213 s <<< FAILURE! > > java.lang.AssertionError: expected [12] but found [11] > > > > Error: > > > testDeadLetterTopicByCustomTopicName(org.apache.pulsar.client.api.DeadLetterTopicTest) > > Time elapsed: 6.152 s <<< FAILURE! > > java.lang.AssertionError: expected [null] but found > > [org.apache.pulsar.client.impl.MessageImpl@7feabb64] > > > > > -- > Jonathan Ellis > co-founder, http://www.datastax.com > @spyced > -- -Ali
