> > So my idea was to suggest to start tracking an exact Jenkins report maybe?
>
> Basing our point of view on the canonical test runs on apache infra makes
> sense to me, assuming that infra is behaving these days. :) Pretty sure
> Mick got that in working order.
It's definitely closing in. Running on donated hosted hardware around
the world has its own challenges, and there's some impl and history in
the jenkins build stuff i'm still uncovering. And stuff that's waiting
on other things (e.g. containerisation). But the main branches look
good. That said it's also a platform that we are capable of breaking
ourselves, now having control over the master.
> - Hard, no compromise position on "we don't RC until all flakes are dead"
I like this. Especially if we are good at entering flakey tests into
jira early. As opposed to entering them all at the last minute and
dashing hopes of the RC.
> > In different conversations with colleagues from the C* community I got the
> > impression that canonical suite (in this case Jenkins) might be the right
> > direction to follow.
> >
> > To be clear, I am always checking any failures seen in any environment and
> > I truly believe that they are worth it to be checked. Not advocating to
> > skip anything! But also, sometimes I feel in many cases CircleCI could
> > provide input worth tracking but less likely to be product flakes. Am I
> > right? In addition, different people use different CircleCI config and see
> > different output. Not to mention flaky tests on Mac running with two
> > cores... Yes, this is sometimes the only way to reproduce some of the
> > reported tests' issues...
One of the predominant unit test failures in Jenkins that is not in
CircleCI, is the…
UnknownHostException: ip-X-X-X-X: ip-X-X-X-X: Name or service not known
See
https://ci-cassandra.apache.org/job/Cassandra-trunk/150/testReport/(root)/_init_/org_apache_cassandra_locator_ReplicaCollectionTest/
Most of these were fixed in CASSANDRA-15622
But the remaining failures are from the use of
`FBUtilities.getLocalAddress()` and `InetAddress.getLocalHost()`. It
affects ci-cassandra because the agents need their public ip so the
master can reach them.
Some help with how best to fix these would be appreciated.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org
