etseidl commented on PR #11267: URL: https://github.com/apache/arrow-rs/pull/11267#issuecomment-6083251519
> /> Job was active longer than specified deadline > > > > So it seems like this benchmark now takes too long to run > > > > Perhaps we can break it up into multiple different benchmarks? Or maybe slim down the matrix of tests? Not just this one. arrow_reader is not far behind. I'd be in favor of splitting these huge ones into more targeted sets. We could run the full suite as separate jobs to hunt for hidden regressions at some interval, but only run the targeted benches during development. This is what we do now with the bench filter, but sometimes it's hard to know what filter to use. -- 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]
