These are chat archives for Snaipe/Criterion

11th
Feb 2016
Dominik
@kaidowei
Feb 11 2016 11:37

@Snaipe hi, I have issues running the criterion tests for the bleeding branch.
The cram_tests failed.

For the other tests, I had to run make test twice and make criterion_unit_tests.

How do I run the cram_tests?
Thanks

Franklin Mathieu
@Snaipe
Feb 11 2016 11:51
@kaidowei you need to install the cram module on python3, then define the PYTHON_BIN environment variable to your python 3 binary.
It's a bit of a hassle right now, but there will be proper checks for cram & python 3 for the stable release
Dominik
@kaidowei
Feb 11 2016 12:09
okay, they run now (with TRAVIS=yes , otherwise, python says "/usr/bin/python3: No module named cram.main; 'cram' is a package and cannot be directly executed")
but 4/15 tests fail, without any changes
is that normal?
Dominik
@kaidowei
Feb 11 2016 12:38

$ simple.c.bin --list
misc: 2 tests

  • ├── failing
  • └── passing
  • \xe2\x94\x9c\xe2\x94\x80\xe2\x94\x80 failing (esc)
  • \xe2\x94\x94\xe2\x94\x80\xe2\x94\x80 passing (esc)

the listing in all cram tests fails.

Franklin Mathieu
@Snaipe
Feb 11 2016 12:39
@kaidowei you are running your tests with python2+cram, rather than python3+cram
Criterion sometimes uses unicode output, and python2 just can't handle it well
Dominik
@kaidowei
Feb 11 2016 12:53
yeah, bit of a hassle... made it working, thanks
Dominik
@kaidowei
Feb 11 2016 13:59
:worried: made a pull request, but something failed, because the build system signaled/killed some tests
Franklin Mathieu
@Snaipe
Feb 11 2016 14:20
@kaidowei there are issues with the regression tests on theories at the moment, your changes aren't causing this
Dominik
@kaidowei
Feb 11 2016 14:22
yes, already saw that. Thanks for the help :)