> The failures generally seem to be coming from Uwe's boxes This may be less about Uwe's boxes, and more due to the fact that all of the "solr'-tagged slaves on the ASF Jenkins have been down for most of a week. So Uwe's boxes are the only things running, by and large.
See the discussions in Slack below for more context, but it's still an open problem that we need help fixing. I've tried to get INFRA's attention on Slack a few days ago without help, and plan to open a ticket tomorrow if there hasn't been any word from them there. Best, Jason [1] https://the-asf.slack.com/archives/CEKUCUNE9/p1727947072229319 [2] https://the-asf.slack.com/archives/CBX4TSBQ8/p1727965062724529 On Thu, Oct 3, 2024 at 6:16 PM Gus Heck <gus.h...@gmail.com> wrote: > > The failures I saw when I downloaded a couple logs centered on threads not > terminated. Perhaps Uwe's box is so overloaded that the shutdown process > for those tests takes too long and the test fails instead? > > On Thu, Oct 3, 2024 at 3:47 PM David Smiley <dsmi...@apache.org> wrote: > > > Relying on people to go look at CI out of the goodness of our hearts is a > > losing strategy. Our contributors don't even know where that is! There > > needs to be a trigger to do so ideally something personalized -- a build > > failure with recent changes that *you* included. Or instead a post/comment > > on linked JIRA or PR -- gets contributor involvement even if the Git > > metadata iacks a real email address. > > > > On Thu, Oct 3, 2024 at 2:46 PM Houston Putman <hous...@apache.org> wrote: > > > > > The failures generally seem to be coming from Uwe's boxes, and I cannot > > > reproduce them locally. The crossDc ones do seem to be failing a lot, but > > > when they fail, it looks like they aren't failing alone. I will continue > > to > > > do research on it though. > > > > > > Our tests are extremely flakey right now, so it's definitely something we > > > need to clean up quickly. Thanks for pointing it out. > > > > > > - Houston > > > > > > On Thu, Oct 3, 2024 at 12:22 PM Gus Heck <gus.h...@gmail.com> wrote: > > > > > > > I went to the fucit jenkins reports site to check on the state of the > > > build > > > > after my recent commit to make sure all was well, but when I got there > > I > > > > was greeted with several weeks of extremely frequent test failures and > > in > > > > the last 2 weeks we seem to have gained several 100% failures (that > > > clearly > > > > preceded my commit). > > > > > > > > http://fucit.org/solr-jenkins-reports/failure-report.html > > > > > > > > This appears to be on fire. > > > > > > > > Clear culprits include the addition of the crossdc module and some > > > problems > > > > with lucene back compatibility indexes There also seems to be a big > > > uptick > > > > in recovery related failures. > > > > > > > > It would be nice if one could filter fucit somehow to see only lucene > > or > > > > only solr, though I imagine that's not a minor undertaking > > > > > > > > -Gus > > > > > > > > -- > > > > http://www.needhamsoftware.com (work) > > > > https://a.co/d/b2sZLD9 (my fantasy fiction book) > > > > > > > > > > > > -- > http://www.needhamsoftware.com (work) > https://a.co/d/b2sZLD9 (my fantasy fiction book) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org For additional commands, e-mail: dev-h...@solr.apache.org
