No worries.. it looks like we didn't update the circleci config in tree for the cassandra-3.0 and cassandra-3.11 branches. We should do that -- i'll take that as an action item on me... for now though you can grab the same one from trunk:
CircleCI Configuration: https://github.com/apache/cassandra/blob/trunk/.circleci/config.yml FYI: kjellman/cassandra-test:0.4.3 is was built from the Docker file as committed here: https://github.com/mkjellman/cassandra-test-docker/blob/master/Dockerfile best, kjellman On Feb 14, 2018, at 10:24 AM, Michael Shuler <mich...@pbandjelly.org<mailto:mich...@pbandjelly.org>> wrote: I apologize for being naive. The test runs do not come from the in-tree circle.yml file and I need to do something different? On 02/14/2018 12:21 PM, Michael Kjellman wrote: please use the latest circleci config that is in trunk. looking at the config you used in your run you’re using the old circleci 1.0 based config. On Feb 14, 2018, at 10:16 AM, Michael Shuler <mich...@pbandjelly.org<mailto:mich...@pbandjelly.org>> wrote: So far, I have had very unpredictable test runs from CirceCI and ASF Jenkins. Commit 890f319 resulted in 4 completely different test failures for me today in CircleCI. https://circleci.com/gh/mshuler/cassandra/150 I trust results from the static ASF slaves even less. `ant test-all -Dtest.name=CommitLogSegmentBackpressureTest` passed for me locally. ¯\_(ツ)_/¯ I do not see any permissions issues in the output of this repeating test failure from our internal Jenkins, but it appears that an instance of Cassandra is left running from some other test, perhaps, and this test cannot bind. I'm fine with cutting a new release set from 890f319 and chalking this up to test flakiness. -- Kind regards, Michael On 02/14/2018 11:50 AM, Michael Kjellman wrote: the tests are writing something to java.io.tmpdir which for whatever reason isn’t writable. the same exact tests work locally and in the cassandra-test docker image. given everyone can partake on circleci runs and asf jenkins i think we should send out those links and base the vote off those runs. On Feb 14, 2018, at 9:48 AM, Michael Shuler <mich...@pbandjelly.org> wrote: This is an internal Jenkins instance that's not reachable on the internet. What's the permissions issue? The test runs on this internal instance are exactly the way cassci used to run - launch a scratch machine, check out, build, run tests. I'll see if I can repro locally. Michael On 02/14/2018 11:44 AM, Michael Kjellman wrote: i looked at this a few weeks back. this is asf jenkins right? if so, it’s a permissions issue on the build executors On Feb 14, 2018, at 9:40 AM, Michael Shuler <mich...@pbandjelly.org> wrote: Thanks for the feedback on 3.0.16 tentative release. Commit 890f319 (current cassandra-3.0 branch HEAD) fails only one test (in both standard and -compression suites) in CI for me. This test has failed 20 times in the last 20 runs. Test output attached. Do we wish to fix this before the next cut, since we're here? :) -- Kind regards, Michael On 02/14/2018 07:30 AM, Jason Brown wrote: I think we can attempt another build and vote now. On Tue, Feb 13, 2018 at 3:44 PM, Jason Brown <jasedbr...@gmail.com> wrote: CASSANDRA-14219 is committed and tests look clean (https://circleci.com/ workflow-run/d0a2622a-e74f-4c46-b0ad-a84ca063736f). On Tue, Feb 13, 2018 at 1:47 PM, Brandon Williams <dri...@gmail.com> wrote: I change my vote to -1 binding as well. On Tue, Feb 13, 2018 at 3:43 PM, Jason Brown <jasedbr...@gmail.com> wrote: -1, binding. Unit tests are broken: https://circleci.com/gh/jasobrown/cassandra/451#tests/containers/50 Dave ninja-committed 7df36056b12a13b60097b7a9a4f8155a1d02ff62 to update some logging messages, which broke ViewComplexTest. The errors like this: junit.framework.AssertionFailedError: Expected error message to contain 'Cannot drop column a on base table with materialized views', but got 'Cannot drop column a on base table table_21 with materialized views.' Dave has a followup commit, 40148a178bd9b74b731591aa46b4158efb16b742, which fixed a few of the errors, but there are four outstanding failures. I created CASSANDRA-14219 last week, and assigned it to Dave, but he might have missed the notification. Dinesh Joshi has a patch that I will review ASAP. Michael, is there a link of where you ran the tests? If so, can you include it in the future [VOTE] emails? Thanks, -Jason On Tue, Feb 13, 2018 at 11:03 AM, Jon Haddad <j...@jonhaddad.com> wrote: +1 On Feb 13, 2018, at 10:52 AM, Josh McKenzie <jmcken...@apache.org> wrote: +1 On Feb 13, 2018 9:20 AM, "Marcus Eriksson" <krum...@gmail.com> wrote: +1 On Tue, Feb 13, 2018 at 1:29 PM, Aleksey Yeshchenko < alek...@apple.com> wrote: +1 — AY On 12 February 2018 at 20:31:23, Michael Shuler ( mich...@pbandjelly.org) wrote: I propose the following artifacts for release as 3.0.16. sha1: 91e83c72de109521074b14a8eeae1309c3b1f215 Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= shortlog;h=refs/tags/3.0.16-tentative Artifacts: https://repository.apache.org/content/repositories/ orgapachecassandra-1154/org/apache/cassandra/apache- cassandra/3.0.16/ Staging repository: https://repository.apache.org/content/repositories/ orgapachecassandra-1154/ Debian and RPM packages are available here: http://people.apache.org/~mshuler *** This release addresses an important fix for CASSANDRA-14092 *** "Max ttl of 20 years will overflow localDeletionTime" https://issues.apache.org/jira/browse/CASSANDRA-14092 The vote will be open for 72 hours (longer if needed). [1]: (CHANGES.txt) https://goo.gl/rLj59Z [2]: (NEWS.txt) https://goo.gl/EkrT4G --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org <3.0-890f319-testall-failure.txt> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org<mailto:dev-unsubscr...@cassandra.apache.org> For additional commands, e-mail: dev-h...@cassandra.apache.org<mailto:dev-h...@cassandra.apache.org> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org<mailto:dev-unsubscr...@cassandra.apache.org> For additional commands, e-mail: dev-h...@cassandra.apache.org<mailto:dev-h...@cassandra.apache.org>
