ra.apache.org/#/,
> however it looks like we've settled back down to ~ 6 failures right now.
>
> On Mon, Mar 27, 2023, at 12:27 PM, Josh McKenzie wrote:
>
> I'll take build lead for the next 2 weeks.
>
> On Sat, Mar 25, 2023, at 4:50 PM, Mick Semb Wever wrote
wn to ~ 6 failures right now.
On Mon, Mar 27, 2023, at 12:27 PM, Josh McKenzie wrote:
> I'll take build lead for the next 2 weeks.
>
> On Sat, Mar 25, 2023, at 4:50 PM, Mick Semb Wever wrote:
>>> Here comes Cassandra CI status for 2023-3-13 - 2023-23-179 :
>>
I'll take build lead for the next 2 weeks.
On Sat, Mar 25, 2023, at 4:50 PM, Mick Semb Wever wrote:
>> Here comes Cassandra CI status for 2023-3-13 - 2023-23-179 :
>>
>> *** CASSANDRA-18338 <https://issues.apache.org/j
>
> Here comes Cassandra CI status for 2023-3-13 - 2023-23-179 :
>
> *** CASSANDRA-18338
> <https://issues.apache.org/jira/browse/CASSANDRA-18338> -
> dtest.bootstrap_test.TestBootstrap.test_cleanup
> trunk
> *** CASSANDRA-18338
> <https://issues.apache.org
Hi all :
Here comes Cassandra CI status for 2023-3-13 - 2023-23-179 :
*** CASSANDRA-18338 <https://issues.apache.org/jira/browse/CASSANDRA-18338>
- dtest.bootstrap_test.TestBootstrap.test_cleanup trunk
*** CASSANDRA-18338 <https://issues.apache.org/jira/browse/CASSANDRA-18338
expiration time should not be negative
On Tue, 21 Feb 2023 at 03:41, guo Maxwell wrote:
>
> Hi all :
> Here comes Cassandra CI status for 2023-2-13 - 2023-2-17 :
>
> *** CASSANDRA-18274 - Test
> Failures:org.apache.cassandra.utils.binlog.BinLogTest.testTruncationReleasesLo
Hi all :
Here comes Cassandra CI status for 2023-2-13 - 2023-2-17 :
*** CASSANDRA-18274 <https://issues.apache.org/jira/browse/CASSANDRA-18274>
- Test
Failures:org.apache.cassandra.utils.binlog.BinLogTest.testTruncationReleasesLogSpace-compression
-linked in 4.1
Other tests below are ti
ira/browse/CASSANDRA-18245> -
Test Failures:
org.apache.cassandra.db.compaction.CompactionsTest.testDontPurgeAccidentally -
linked in 3.11
-
From: Dan Jatnieks
Sent: Friday, February 10, 2023 2:42 PM
To: dev@cassandra.apache.org ; Claude Warren, Jr
Subject
New Failures from Build Lead Week 6:
*** CASSANDRA-18021 - Flaky
org.apache.cassandra.distributed.test.ReprepareTestOldBehaviour#testReprepareMixedVersionWithoutReset
- This existing ticket has been linked in butler to new failures on 3.11
*** CASSANDRA-17608 - Fix testMetricsWithRebuildAndStream
New Failures from Build Lead Week 5
*** CASSANDRA-18198 - "AttributeError: module 'py' has no attribute 'io'"
reported in multiple tests
- reported in 4.1, 3.11, and 3.0
- identified as a possible class loader issue associated with
CASSANDRA-18150
*** CASSANDRA-18191 - Native Transport SSL tests
New failures from Build Lead Week 4:
*** CASSANDRA-18188 - Test failure in
upgrade_tests.cql_tests.cls.test_limit_ranges
- trunk
- AttributeError: module 'py' has no attribute 'io'
*** CASSANDRA-18189 - Test failure in
cqlsh_tests.test_cqlsh_copy.TestCqlshCopy.test_bulk_round_trip_with_timeouts
-
>
> *** The Butler (Build Lead)
>
> The introduction of Butler and the Build Lead was a wonderful
> improvement to our CI efforts. It has brought a lot of hygiene in
> listing out flakies as they happened. Noted that this has in-turn
> increased the burden in getting our major releases out, but t
> I don't believe it warrants a CEP, speak up if you disagree.
I agree with this but I'm also biased having been working w/you on this for a
bit.
My instinct is that most folks on the project want CI that works consistently,
quickly, and is minimally complex to modify. So the less disruptive an
Happy 2023 everyone!
With only four months in front of us before the first 5.0 release I'm
hoping we can re-energize our focus on CI and Stable Trunk.
This post covers the following
* Recap of CI improvements
* State of Affair
* The Butler (Build Lead)
* Proposal for a Repeatable Container
This is awesome! Thanks Mick for all the great work.
~Charles
On Mon, Aug 10, 2020 at 11:41 AM Ekaterina Dimitrova
wrote:
>
> Thank you Mick for all the work you are doing for the C* CI and not only!
> I am especially excited about the addition of the upgrade tests.
> It’s also great that things
Thank you Mick for all the work you are doing for the C* CI and not only!
I am especially excited about the addition of the upgrade tests.
It’s also great that things got documented.
Best regards,
Ekaterina
On Sat, 8 Aug 2020 at 6:41, Mick Semb Wever wrote:
> The following is a summary of chang
The following is a summary of changes, status, and suggestions to our
community CI, ci-cassandra.apache.org
Please reply with questions, as well as any input on CircleCI status anyone
has to offer.
This post will touch on…
* Upgrade Tests
* Build Times and Improvements
* Pre Commit Bui
The following is a summary of changes and status over the past ~month.
Shout outs go to David Capwell, Ekaterina Dimitrova, Eduard
Tudenhöfner, Berenguer Blasi, Anthony Grasso, and Dinesh Joshi, for
with testing framework issues.
** New CI-Cassandra landing page
The default landing page for htt
I spoke with Mick offline about this a bit but wanted to relay it here for
posterity:
** Why are cdc and compression unit tests run separately?
>
In the case of cdc, I erred on the side of caution in impl assuming that
most people would not be using it so any degradation in performance for the
non
It's been three weeks since the last update¹. What follows is a quick
state of affairs and a few questions for anyone to jump in and help
with.
The ASF CI is running at
https://ci-cassandra.apache.org/view/branches/ and will soon have 36
builds agents in total. Thanks to Instaclustr, Amazon, ilan
Thanks for working on this, Mick. I think I'll have some time next week to
help out.
On Fri, Mar 13, 2020 at 5:38 AM Mick Semb Wever wrote:
>
> The ASF new Jenkins setup is almost complete.
> See https://ci-cassandra.apache.org/view/branches/
> The setup has been tracked in INFRA-19951
>
> The
The ASF new Jenkins setup is almost complete.
See https://ci-cassandra.apache.org/view/branches/
The setup has been tracked in INFRA-19951
The next step here is to retire our usage of `builds.apache.org` and move all
existing agents to the new setup. There are also new agents getting ready to
I would love to get involved promoting those if and when a list produced.
Could this be something as a Cassandra confluence page? I would be happy to
volunteer some time keeping that up-to-date.
Patrick
On Fri, Jan 24, 2020 at 6:49 AM Joshua McKenzie
wrote:
> >
> > an entry in the progress repo
>
> an entry in the progress report?
That'd be slick. I've had some people pinging me on slack asking about the
easiest way to get involved with the project and ramp up, and I think
refactoring and cleaning up a dtest or two would be another vector for
people to get their feet wet. I like it!
On
> > - parallelise dtests (because 12 hours is wild)
>
> That's one word for it. :)
>
> We used to ad hoc take a crack at sorting the individual test times by
> longest and taking top-N and seeing if there was LHF to shave off that.
> Being on a flight atm, not having that data handy right now
>
> - parallelise dtests (because 12 hours is wild)
That's one word for it. :)
We used to ad hoc take a crack at sorting the individual test times by
longest and taking top-N and seeing if there was LHF to shave off that.
Being on a flight atm, not having that data handy right now, and that not
> > If I don't hear any objection, I'll commit this. Off this, as it
> > aggregates test reports, it's now possible to start test posting emails
> > with the test report summary, as well as bringing in the dtest builds
> > into the pipeline.
>
>
> Based on the pipeline approach I've gotten
> If I don't hear any objection, I'll commit this. Off this, as it
> aggregates test reports, it's now possible to start test posting emails
> with the test report summary, as well as bringing in the dtest builds
> into the pipeline.
Based on the pipeline approach I've gotten notifications
> Moving to pure pipeline jobs with all build & test runs in one pipeline,
> with a final single JIRA comment post operation of all the results in
> one comment would be the only way I can think of to prevent the
> multi-post problem.
For the pipeline build, this is what I have so far puttin
On 1/11/20 10:02 AM, Mick Semb Wever wrote:
This brings up the issue that links to builds on tickets should
ideally refer to information that is permanent. This could be
done by configuring builds to keep status and logs but not the
built artefacts (and/or adding bigger disks). I will now up
On 1/11/20 9:17 AM, Michael Shuler wrote:
On 1/11/20 4:48 AM, Mick Semb Wever wrote:
This brings up the issue that links to builds on tickets should
ideally refer to information that is permanent.
This could be done by configuring builds to keep status and logs but
not the built artefact
> > This brings up the issue that links to builds on tickets should ideally
> > refer to information that is permanent.
> > This could be done by configuring builds to keep status and logs but not
> > the built artefacts (and/or adding bigger disks). I will now update the
> > builds to discard
On 1/11/20 4:48 AM, Mick Semb Wever wrote:
This brings up the issue that links to builds on tickets should ideally refer
to information that is permanent.
This could be done by configuring builds to keep status and logs but not the
built artefacts (and/or adding bigger disks). I will now up
> I would still be in favour of adding the post-commit CI feedback
> integration, though in a shorter format that what Hadoop does. It's a
> nice finalising comment on the ticket. Maybe we can come back to this
> once we stabilise Jenkins a bit more and ask what everyone thinks? (For
> exampl
> Thank you for getting this fixed, Mick! Would it be possible to provide
> CI feedback on Jira tickets?
Yes, i know that Hadoop does this.
For example
https://issues.apache.org/jira/browse/HADOOP-16697?focusedCommentId=17012760&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-t
Thank you for getting this fixed, Mick! Would it be possible to provide CI
feedback on Jira tickets?
Dinesh
> On Jan 8, 2020, at 12:34 AM, Mick Semb Wever wrote:
>
>
> I'm chuffed to say that ASF Jenkins builds for branches 2.2, 3.0, 3.11, and
> trunk, are now all working.
>
> Trunk: https
>
> On my 16gb quad i7 laptop dtests take 4-5 hours
Hm. This is actually faster than I'd have expected so that's a positive for
my Friday :). Makes me wonder how things would behave on one of the new
threadrippers w/PCIe-4.
And yes, I'm looking for excuses to get one of those.
On Fri, Jan 10, 20
> We had roughly 7 jenkins slaves DS had donated languish I'm looking into
> (came up on slack yesterday morning) so hopefully we'll have some more
> resources back in the pool soon.
Thanks Josh!
Currently all the hardware is provided by Instaclustr.
Any hardware for running dtests, from any
Thanks for taking this on Mick.
We had roughly 7 jenkins slaves DS had donated languish I'm looking into
(came up on slack yesterday morning) so hopefully we'll have some more
resources back in the pool soon.
One other thing we've seen repeatedly over the years is startlingly
low-hanging-fruit of
I'm chuffed to say that ASF Jenkins builds for branches 2.2, 3.0, 3.11, and
trunk, are now all working.
Trunk: https://builds.apache.org/view/A-D/view/Cassandra%20trunk/
3.11: https://builds.apache.org/view/A-D/view/Cassandra%203.11/
3.0: https://builds.apache.org/view/A-D/view/Cassa
40 matches
Mail list logo
