Hi, I must admit that I have been surprised by this merge and this following email. We had lengthy discussions recently and the final agreement was that the requirement for a merge was a green CI. I could understand that for some reasons as a community we could wish to make some exceptions. In this present case there was no official discussion to ask for an exception. I believe that this merge creates a bad precedent where anybody can feel entitled to merge without a green CI and disregard any previous community agreement.
Le sam. 25 nov. 2023 à 09:22, Mick Semb Wever <m...@apache.org> a écrit : > > Great work Sam, Alex & Marcus ! > > > >> There are about 15-20 flaky or failing tests in total, spread over >> several test jobs[2] (i.e. single digit failures in a few of these). We >> have filed JIRAs for the failures and are working on getting those fixed as >> a top priority. CASSANDRA-19055[3] is the umbrella ticket for this follow >> up work. >> >> There are also a number of improvements we will work on in the coming >> weeks, we will file JIRAs for those early next week and add them as >> subtasks to CASSANDRA-19055. >> > > > Can we get these tests temporarily annotated as skipped while all the > subtickets to 19055 are being worked on ? > > As we have seen from CASSANDRA-18166 and CASSANDRA-19034 there's a lot of > overhead now on 5.0 tickets having to navigate around these failures in > trunk CI runs. > > Also, we're still trying to figure out how to do repeated runs for a patch > so big… (the list of touched tests was too long for circleci, i need to > figure out what the limit is and chunk it into separate circleci configs) … > and it probably makes sense to wait until most of 19055 is done (or tests > are temporarily annotated as skipped). > > >
