GitLab

This should change nothing, we should never go to the '?'.

As noted by @mikael-s, e963e165 hided a failed test in vidjil_revcomp_s22.should_get.
This test is one challenging sequence from Stanford-S22:
we currently do not find the same window on the sequence and on its revcomp.

valgrind_should: valgrind on functional tests
valgrind_tests:  valgrind on unit tests

pip install unittest2
pip install unittest-xml-reporting
python web2py.py -S vidjil -M -R testRunner.py
output folder > server/web2py/test-reports

This test was too long. We now just check the first 1000 reads and the main clone.

This invocation should also be more portable
See http://stackoverflow.com/questions/2792675/how-portable-is-mktemp1

By default the launcher is put at the start of the command line. In some cases
it must not be at the start and in other cases we don't want to use valgrind
(or another launcher) so we deactivate it with the !NO_LAUNCHER: directive

If we find it, we don't add it at the beginning (see doc.)

Makefile: For tests ensure that vidjil is rebuilt with -O0 -g so that we get useful information with Valgrind (slower...)

Use " rather than ' so that LAUNCHER can be expanded
which is useful when LAUNCHER contains some bash commands.

This allows to launch the script from another directory while
still benefiting from the default otions -p and -q.

If we overwrite the_kseg (in case it exists), it is definitely lost and we have a memory leak.

We do not want to have red everywhere in the default view.