uschindler commented on issue #15662: URL: https://github.com/apache/lucene/issues/15662#issuecomment-3864660255
> Yeah, +1, I'll make this switch after surviving the current situation once dust settles ... it'd be nice to get a clean read on that (swap it when there are no real lucene/luceneutil changes at the same time ...). Hmm we need a day when lucene devs are gonna be idle ... I think the biggest problem on the last change was the long "downtime" of the benchmark. It stopped working on Jan 22 and came back on Jan 29. So the changes caused by the updates were in line with many merged PRs in the same timeframe. Normally when we do hardware/software/config changes we should make sure that we monitor the followup runs and fix bugs in the benchmark (like adapting the CFS changes) fast. Maybe we should have some way to actually test the benchmarker code. How about adding the benchmarker under dev-tools together with the other python scripts (using package manager "uv"? @rmuir -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
