Hello, We use the circleci tests splitter to split by timings, and it seems that whenever we have a failed build, the build immediately after it does a very poor job splitting files among containers. This only seems to the first build after a failed build. Even if that (second) build fails though,…

No, they’re separate issues. I filed both of these. That one has to do with under-reporting test times when splitting by file. This one is about what build circle bases timing decisions off of.

Build failures seem to wipe out test timings for subsequent builds

Feedback & Bug Reports

halfer February 23, 2018, 1:11pm 2

Is this related to, or a duplicate of, this question?

Topic		Replies	Views
"No timing found for" the same few test files on every new branch Running Tests ruby	2	245	March 14, 2025
Splitting go tests by timing in circleci Running Tests	0	2008	February 5, 2020
CircleCI tests split does not work as advertised Running Tests parallelism	3	4801	November 17, 2020
Build times-out for a single user Feedback & Bug Reports	0	979	March 9, 2016
Split by timing parallelism does not seem to balance out Running Tests parallelism	3	3408	January 2, 2019

Build failures seem to wipe out test timings for subsequent builds

Related topics