On Wed, 12 Jan 2022 at 07:23, Joseph Lynch wrote:
> On Tue, Jan 11, 2022 at 4:48 PM Joshua McKenzie
> wrote:
> >> If this vote passes would that mean we cannot cut any release
> >
> > We would not cut a release with known failing tests, no. Which for
> critical infrastructure software _seems_ li
On Tue, Jan 11, 2022 at 4:48 PM Joshua McKenzie wrote:
>> If this vote passes would that mean we cannot cut any release
>
> We would not cut a release with known failing tests, no. Which for critical
> infrastructure software _seems_ like it should probably be table stakes, no?
>
While I very mu
On Wed, Jan 12, 2022 at 12:47 AM Berenguer Blasi
wrote:
>
> We shouldn't be at 15-20 failures but at 2 or 3. The problem is that those 2
> or 3 have already been hammered for over a year by 2 or 3 different
> committers and they didn't crack.
>
Last I checked circleci was almost fully green on
We shouldn't be at 15-20 failures but at 2 or 3. The problem is that
those 2 or 3 have already been hammered for over a year by 2 or 3
different committers and they didn't crack.
On 11/1/22 22:47, Joshua McKenzie wrote:
>
> this seems problematic given all four
> release branches (2.2, 3.0
>
> this seems problematic given all four
> release branches (2.2, 3.0, 3.11, 4.0) + trunk appear to have about
> 15-20 failures on ci-cassandra.apache.org
That's the intended outcome of making it a hard blocker for release: it
incentivizes us fixing these tests.
If this vote passes would that me
> No release can be cut without a fully green CI run on ci-cassandra.apache.org
I appreciate the goal but this seems problematic given all four
release branches (2.2, 3.0, 3.11, 4.0) + trunk appear to have about
15-20 failures on ci-cassandra.apache.org at the time of this vote. If
this vote passe
+1
On Tue, Jan 11, 2022 at 7:02 AM Andrés de la Peña
wrote:
> +1
>
> On Tue, 11 Jan 2022 at 13:45, Joshua McKenzie
> wrote:
>
>> If my understanding is correct, we run the canonical set *before* merging,
>>> and the runs triggered by the cassandra CI bot include the full set
>>> *after* a commi
+1
On Tue, 11 Jan 2022 at 13:45, Joshua McKenzie wrote:
> If my understanding is correct, we run the canonical set *before* merging,
>> and the runs triggered by the cassandra CI bot include the full set
>> *after* a commit is merged.
>
> Good point. Clarified to indicate it's canonical *circlec
>
> If my understanding is correct, we run the canonical set *before* merging,
> and the runs triggered by the cassandra CI bot include the full set
> *after* a commit is merged.
Good point. Clarified to indicate it's canonical *circleci tests* to run
before merging, and the ci-cassandra jenkins i
On Mon, 10 Jan 2022 at 20:00, Joshua McKenzie wrote:
> Wiki draft article here:
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=199530280
>
+1
small nits:
- none of the other confluence pages use the "Apache" prefix
- can it reference the CI Systems page please
- post-vote:
Hi Anthony,
Great news! Thanks everyone for all the work and time invested. IMHO docs
are as important as well written code.
“Would we reopen it to fix the problem or would we open a new ticket? Do we
have project guidelines around this? I would think in this scenario a new
ticket would be create
+1, same note as David
On Tue, 11 Jan 2022 at 4:54, Benjamin Lerer wrote:
> +1
>
> Le mar. 11 janv. 2022 à 07:09, Berenguer Blasi
> a écrit :
>
>> +1
>>
>> On 10/1/22 20:00, Joshua McKenzie wrote:
>> > Wiki draft article
>> > here:
>> https://cwiki.apache.org/confluence/pages/viewpage.action?pa
+1
Le mar. 11 janv. 2022 à 07:09, Berenguer Blasi a
écrit :
> +1
>
> On 10/1/22 20:00, Joshua McKenzie wrote:
> > Wiki draft article
> > here:
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=199530280
> > <
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=199
13 matches
Mail list logo
