> - No flaky tests according to Jenkins or CircleCI? Also, some people run
> the free tier, others take advantage of premium CircleCI. What should be
> the framework?
It would be good to have a common understanding of this; my current mental
model is
1) Jenkins
2) Circle CI Free tear unit tests
I cant see your profiler image so I may be missing something.
I remember looking at this in past too. At least with 3.x version of
java client the stream ids are reused as released so low volume apps wont
have much overhead and highly concurrent ones it prevents allocating
20-100k objs/sec. I thin
Good point Jordan re: flaky test being either implying API instability or
blocker to ability to beta test.
On Thu, May 28, 2020 at 12:56 PM Jordan West wrote:
> > On Wed, May 27, 2020 at 5:13 PM Ekaterina Dimitrova <
> > ekaterina.dimitr...@datastax.com> wrote:
>
> > - No flaky tests according
> On Wed, May 27, 2020 at 5:13 PM Ekaterina Dimitrova <
> ekaterina.dimitr...@datastax.com> wrote:
> - No flaky tests according to Jenkins or CircleCI? Also, some people run
> > the free tier, others take advantage of premium CircleCI. What should be
> > the framework?
While I agree that we shou
Hello,
Could you please help to understand the purpose of a particular part of
code in Cassandra
codebase: org.apache.cassandra.transport.ServerConnection#getQueryState
https://github.com/apache/cassandra/blob/cassandra-3.11.6/src/java/org/apache/cassandra/transport/ServerConnection.java#L46
I not
Agree re: 15299.
This thread is about pushing out flaky tests and what we define as that
cohort as I understand it.
On Thu, May 28, 2020 at 7:59 AM Ekaterina Dimitrova
wrote:
> CASSANDRA-15299 - All interface-related still open tickets are blockers.
> My point was that they are already just a
CASSANDRA-15299 - All interface-related still open tickets are blockers.
My point was that they are already just a few, looking into Jira. So except
them, flaky tests are really a thing that requires attention.
Also, I agree with Mick that it’s good to have a plan and opened Jira
tickets earlier
`ant test` made it through several hundred test suites before it died:
apache-cassandra-4.0-alpha4-src/build.xml:1927: java.lang.OutOfMemoryError:
Java heap space
Some individual tests also error out with an OOM, e.g.
IndexSummaryTest#testLargeIndexSummary.
Best,
Angelo
On Mon, May 25, 2020 at 1
> I have the feeling that the thing that prevents us primarily from
cutting beta at the moment is flaky tests
CASSANDRA-15299 is still in progress and I think we have to consider it a
blocker, given that beta "should be interface-stable, so that consumers do not
have to incur any code changes on
>
> 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 t
> > 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. Runn
11 matches
Mail list logo
