Do a quick test iteration here, I guess: https://github.com/Snaipe/Criterion/blob/bleeding/src/io/xml.c#L168
if you want to regenerate the new tests outputs, simply call
make cram_tests CRAM=-i
I'll roll this out for 2.3.0
can you check for me, if the time is accounted correctly?
I have a sleep in my test and the time is still 0.00
with 2.2.1 it works
let me investigate
oh, right, I remember why
that's because the protocol started working with timestamps rather than elapsed times
and currently timestamps aren't implemented
I ought to make an issue so I don't forget
if ctest does nothing, then you probably have to run
cmake -DCTESTS=ON -DDEV_BUILD=ON .. from your build directory
they're running now
where can I see the results of the cram test?
it just says, it failed
install cram 0.6 with
sudo pip install cram==0.6 (or with --user if you don't want to install it in /usr)
in doubt, run
make cram_tests
and to troubleshoot with
ctest, you need to pass it an option
let me check which one
--output-on-failure
[100%] Built target criterion_samples
CMake Error at /*beep*/Criterion/.cmake/Modules/Cram.cmake:66 (message):
Cram tests failed
make[3]: *** [cram_tests] Error 1
make[2]: *** [test/CMakeFiles/cram_tests.dir/all] Error 2
make[1]: *** [test/CMakeFiles/cram_tests.dir/rule] Error 2
make: *** [cram_tests] Error 2
let me check on my end
oh, it's a bug in the cmake module, somehow
try
export PYTHON_BIN=python3
and re-run the tests
I'll push a fix to address the case where
PYTHON_BIN isn't set
do you think, xml parsers mind?