Hello David, I can take a closer work, but here's how you can debug it yourself: 1. Repro it on not-Travis (given that it's a solver error, should be easy) 2. Turn on -v 3. Look through the entrails to see why criterion is not satisfiable. Maybe even just look at the dependencies in the benchmarks section. Could it be a cyclic dependency problem? Edward Excerpts from David Feuer's message of 2016-09-02 01:04:33 -0400:
Gabriel Gonzalez has gotten Cabal benchmark integration working for containers, and then I broke it without realizing I'd done so because Travis CI wasn't building the benchmarks. When I got them working again locally and tried enabling them in .travis.yml (just adding --enable-benchmarks to the cabal configure line), things went kablooey: https://travis-ci.org/haskell/containers/jobs/156997144
Does anyone know how to interpret those entrails? Is this something that can be fixed?