another thought is to have the
sufficient_system_resources_for_resource_intensive_tests fixture dynamically
figure out the number of threads to run stress with. seems reasonable we should
significantly lower our concurrency dynamically when we are resource
constrained.
> On Jan 10, 2018, at 1
i had done some limited testing on the medium size an didn't see quite as bad
behavior you were seeing... :\
i added a test fixture
(sufficient_system_resources_for_resource_intensive_tests) that just currently
does a very very basic check free memory check and deselects tests annotated
with t
I was giving this another try today to see how long it would take to
finish on a oss account. But I've canceled the job after some hours as
tests started to fail almost constantly.
https://circleci.com/gh/spodkowinski/cassandra/176
Looks like the 2CPU/4096MB (medium) limit for each container isn'
> This is a huge improvement in runtime (understatement of the day award…
Agreed 100%. Love what I’m seeing here. Anything that improves the ease and
accessibility of testing is awesome in my book. Apologies for not being
involved in the fixes, I had intended to contribute over the break but
plan of action is to continue running everything on asf jenkins.
in additional all developers (just like today) will be free to run the unit
tests and as many of the dtests as possible against their local test branches
in circleci. circleci offers a free OSS account with 4 containers. while it
>
> 1) have *all* our tests run on *every* commit
Have we discussed the cost / funding aspect of this? I know we as a project
have run into infra-donation cost issues in the past with differentiating
between ASF as a whole and cassandra as a project, so not sure how that'd
work in terms of sponsor
