i've seen it timeout a lot too. if you think breaking it up will fix it that definitely sounds like a good approach!
> On Feb 27, 2018, at 2:57 PM, Dikang Gu <[email protected]> wrote: > > I took some look at the cql3.ViewTest, it seems too big and timeout very > often. Any objections if I split it into two or multiple tests? > > On Tue, Feb 27, 2018 at 1:32 PM, Michael Kjellman <[email protected]> > wrote: > >> well, turns out we already have a jira tracking the MV tests being broken >> on trunk. they are legit broken :) thanks jaso >> >> https://issues.apache.org/jira/browse/CASSANDRA-14194 >> >> not sure about the batch test timeout there though.. did you debug it at >> all by chance? >> >> >> On Feb 27, 2018, at 1:27 PM, Michael Kjellman <[email protected]<mailto: >> [email protected]>> wrote: >> >> hey dikang: just chatted a little bit about this. proposal: let's add the >> equivalent of @resource_intensive to unit tests too.. and the first one is >> to stop from running the MV unit tests in the free circleci containers. >> thoughts? >> >> also, might want to bug your management to see if you can get some paid >> circleci resources. it's game changing! >> >> best, >> kjellman >> >> On Feb 27, 2018, at 12:12 PM, Dinesh Joshi <[email protected]. >> INVALID<mailto:[email protected]>> wrote: >> >> Some tests might require additional resources to spin up the required >> components. 2 CPU / 4GB might not be sufficient. You may need to bump up >> the resources to 8CPU / 16GB. >> Dinesh >> >> On Tuesday, February 27, 2018, 11:24:34 AM PST, Dikang Gu < >> [email protected]<mailto:[email protected]>> wrote: >> >> Looks like there are a few flaky/timeout unit tests in trunk, wondering is >> there anyone looking at them already? >> >> testBuildRange - org.apache.cassandra.db.view.ViewBuilderTaskTest >> testUnloggedPartitionsPerBatch - >> org.apache.cassandra.metrics.BatchMetricsTest >> testViewBuilderResume - org.apache.cassandra.cql3.ViewTest >> >> https://circleci.com/gh/DikangGu/cassandra/20 >> >> -- >> Dikang >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected]<mailto:dev- >> [email protected]> >> For additional commands, e-mail: [email protected]<mailto: >> [email protected]> >> >> >> > > > -- > Dikang --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
