Okie. Would create 1 issue per such group of tests and add the "heisenbugs" label to them. Would link various details also Chetan Mehrotra
On Tue, Apr 3, 2018 at 11:42 AM, Rodric Rabbah <[email protected]> wrote: > Hi Chetan, yes please create issues - I had created a label "heisenbugs" in > the issue tracker for such failures. > > KafkaConnectorTests I think is one we've seen before but I don't see it > here > https://github.com/apache/incubator-openwhisk/issues?q=is%3Aopen+is%3Aissue+label%3Aheisenbug > > On Tue, Apr 3, 2018 at 1:36 AM, Chetan Mehrotra <[email protected]> > wrote: > >> I am seeing few tests failing often on Travis. The failure looks like >> not related to changes in the PR (as same build passes on next try or >> on branch build on fork). For e.g. following few failures are often >> seen >> >> 1. LoadBalancerDataTests >> >> - https://scans.gradle.com/s/w3sgwosixzohk/tests/failed >> - https://scans.gradle.com/s/7gztyfsgyxm6a/tests/failed >> >> 2. KafkaConnectorTests >> >> - https://scans.gradle.com/s/p4wqdppt34ilo/tests/failed >> >> 3. ReplicatorTests >> >> - https://scans.gradle.com/s/q5yuacsmjvhwc/tests/failed >> >> Should we create 1 issue and collect links/stats there such that they >> can be later relooked and made resilient? >> >> Chetan Mehrotra >>
