testsuite fails 15 tests

Issue #917 new
Jonas Smedegaard created an issue

Hi,

When building release 0.6.1, testsuite fails the following tests:

FAIL!  : TST_TapeCommandLine::OpenMeasurements(Send wrong path to a file) 'exit == exitCode' returned FALSE. (The start operation timed out or an error occurred.
FAIL!  : TST_TapeCommandLine::OpenMeasurements(Old individual format to new version) 'exit == exitCode' returned FALSE. (The start operation timed out or an error occurred.
FAIL!  : TST_TapeCommandLine::OpenMeasurements(Open empty file) 'exit == exitCode' returned FALSE. (The start operation timed out or an error occurred.
FAIL!  : TST_TapeCommandLine::OpenMeasurements(Open the VIT file with all know measurements (v0.3.0)) 'exit == exitCode' returned FALSE. (The start operation timed out or an error occurred.
FAIL!  : TST_TapeCommandLine::OpenMeasurements(Open the VST file with all know measurements (v0.4.0)) 'exit == exitCode' returned FALSE. (The start operation timed out or an error occurred.
FAIL!  : TST_TapeCommandLine::OpenMeasurements(Open the VST file for man ru GOST (v0.3.0).) 'exit == exitCode' returned FALSE. (The start operation timed out or an error occurred.
FAIL!  : TST_TapeCommandLine::OpenMeasurements(Open the VIT file with all know measurements (v0.3.3)) 'exit == exitCode' returned FALSE. (The start operation timed out or an error occurred.
FAIL!  : TST_TapeCommandLine::OpenMeasurements(Open the VST file with all know measurements (v0.4.2)) 'exit == exitCode' returned FALSE. (The start operation timed out or an error occurred.
FAIL!  : TST_TapeCommandLine::OpenMeasurements(Open the VST file for man ru GOST (v0.4.2).) 'exit == exitCode' returned FALSE. (The start operation timed out or an error occurred.
FAIL!  : TST_TapeCommandLine::OpenMeasurements(Broken file. Not unique name.) 'exit == exitCode' returned FALSE. (The start operation timed out or an error occurred.
FAIL!  : TST_TapeCommandLine::OpenMeasurements(Broken file. Measurement name can't be empty.) 'exit == exitCode' returned FALSE. (The start operation timed out or an error occurred.
FAIL!  : TST_TapeCommandLine::OpenMeasurements(Broken file. An empty value shouldn't break a file.) 'exit == exitCode' returned FALSE. (The start operation timed out or an error occurred.
FAIL!  : TST_TapeCommandLine::OpenMeasurements(Broken file. Invalid measurement name.) 'exit == exitCode' returned FALSE. (The start operation timed out or an error occurred.
FAIL!  : TST_TapeCommandLine::OpenMeasurements(Empty text VIT file.) 'exit == exitCode' returned FALSE. (The start operation timed out or an error occurred.
FAIL!  : TST_TapeCommandLine::OpenMeasurements(Empty text VST file.) 'exit == exitCode' returned FALSE. (The start operation timed out or an error occurred.

Comments (10)

  1. Jonas Smedegaard reporter

    Ok, then it might be my environment that need to be educated more about where to find the freshly built libraries (since your build framework doesn't handle that). Thanks! That is possibly enough to clue me in on how to solve this...

  2. Roman Telezhynskyi repo owner

    You need something like this: export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:"$TRAVIS_BUILD_DIR/build/src/libs/vpropertyexplorer/bin:$TRAVIS_BUILD_DIR/build/src/libs/qmuparser/bin";

  3. Jonas Smedegaard reporter

    Yeah, I already have something like that (otherwise a lot more would fail).

    Odd thing (to me) is that only those 15 tests fail. My suspicion is that I need to pass those at more/different places (e.g. if those test calls ignore environment variables, perhaps when done in combination with xvfb...

  4. Jonas Smedegaard reporter

    Build succeeds now, changing only how make is initiated.

    Could it be that those tape tests may fail if run in parallel mode - i.e. make -j4 ?

  5. Roman Telezhynskyi repo owner

    Could it be that those tape tests may fail if run in parallel mode - i.e. make -j4 ?

    No, i don't think so. Calling tests is not related to make -j4. It is separate command.

    This is how i call tests: xvfb-run -a make --silent check TESTARGS="-silent";

    It's hard to say what is wrong without actual error message.

  6. Jonas Smedegaard reporter

    How would you get actual error messages?

    Even without those silencing hints the build framework is by default silent. By build is patched to not silence make targets, but I am unaware how to make testsuite more verbose.

    Quoting Roman Telezhynskyi (2019-01-01 17:47:22)

  7. Roman Telezhynskyi repo owner

    @jonassmedegaard, take this commit, maybe stderr contains error. Also you can try to change it to readAllStandardOutput().

  8. Log in to comment