There's currently a gap in the benchmark history (see eg GRO.GROReadBench.time_read_GRO_coordinates) between MDAnalysis/mdanalysis@b113fd51 (after 2.9.0) and MDAnalysis/mdanalysis@58b872b8 (before 2.10.0).
When c3potato's OS was upgraded together with the ASV installation and we switched to conda envs to make it all work again 4a9069d and then increased coverage to python 3.14 8737b39 we tried to run all the commits that had failed since ~Summer 2025 (using something like asv run --config asv_c3potato.conf.json -e -j 4 "release-2.9.0..HEAD --merges" but a gap remained.
There's currently a gap in the benchmark history (see eg GRO.GROReadBench.time_read_GRO_coordinates) between MDAnalysis/mdanalysis@b113fd51 (after 2.9.0) and MDAnalysis/mdanalysis@58b872b8 (before 2.10.0).
When c3potato's OS was upgraded together with the ASV installation and we switched to conda envs to make it all work again 4a9069d and then increased coverage to python 3.14 8737b39 we tried to run all the commits that had failed since ~Summer 2025 (using something like
asv run --config asv_c3potato.conf.json -e -j 4 "release-2.9.0..HEAD --merges"but a gap remained.