some shell recorder tests fail

[markus2330]

might be some local problem but in any case the exports should not differ?

        Start 122: testshell_mathcheck
122/187 Test #122: testshell_mathcheck ......................***Failed    2.71 sec
kdb mount mathcheck.esr user/tmount/mathcheck mathcheck ni
kdb set user/tmount/mathcheck/check/test0/points 5.9
kdb set user/tmount/mathcheck/check/test1/points 4.5
kdb set user/tmount/mathcheck/check/gp
kdb setmeta user/tmount/mathcheck/check/gp check/math ":= + ../test0/points ../test1/points"
kdb get user/tmount/mathcheck/check/gp
kdb rm -r user/tmount/mathcheck
kdb set user/tmount/mathcheck/check/gp/test0/points 5.9
kdb set user/tmount/mathcheck/check/gp/test1/points 4.5
kdb set user/tmount/mathcheck/check/gp
kdb setmeta user/tmount/mathcheck/check/gp check/math ":= + ./test0/points ./test1/points"
kdb get user/tmount/mathcheck/check/gp
kdb rm -r user/tmount/mathcheck
kdb set user/tmount/mathcheck/check/test0/points 5.9
kdb set user/tmount/mathcheck/check/test1/points 4.5
kdb set user/tmount/mathcheck/check/gp
kdb setmeta user/tmount/mathcheck/check/gp check/math ":= + @/check/test0/points @/check/test1/points"
kdb get user/tmount/mathcheck/check/gp
kdb rm -r user/tmount/mathcheck
kdb set user/tmount/mathcheck/key0 5
kdb set user/tmount/mathcheck/sum
kdb setmeta user/tmount/mathcheck/sum check/math ":= + @/key0 @/key1"
kdb get user/tmount/mathcheck/sum
kdb rm -r user/tmount/mathcheck
kdb set user/tmount/mathcheck/key0 5
kdb set user/tmount/mathcheck/sub
kdb setmeta user/tmount/mathcheck/sub check/math ":= - @/key0 @/key1"
kdb get user/tmount/mathcheck/sub
kdb rm -r user/tmount/mathcheck
kdb set user/tmount/mathcheck/key0 5
kdb set user/tmount/mathcheck/mul
kdb setmeta user/tmount/mathcheck/mul check/math ":= * @/key0 @/key1"
kdb get user/tmount/mathcheck/mul
kdb rm -r user/tmount/mathcheck
kdb set user/tmount/mathcheck/key0 5
kdb set user/tmount/mathcheck/div
kdb setmeta user/tmount/mathcheck/div check/math ":= / @/key0 @/key1"
kdb get user/tmount/mathcheck/div
kdb set user/tmount/mathcheck/check/a 3.1
kdb set user/tmount/mathcheck/check/b 4.5
kdb set user/tmount/mathcheck/check/k 7.6
kdb setmeta user/tmount/mathcheck/check/k check/math "== + ../a ../b"
kdb set user/tmount/mathcheck/check/k 7.7
kdb rm -r user/tmount/mathcheck
kdb umount user/tmount/mathcheck
Binärdateien /tmp/tmp.9696FiZ4zo/user.export.dump und /tmp/tmp.9696FiZ4zo/user.check.dump sind verschieden.
Test did not leave user config in the same state at is was before!
This means the test itself is flawed!
You can inspect the original user config in /tmp/tmp.9696FiZ4zo/user.export.dump
compared to situation now in /tmp/tmp.9696FiZ4zo/user.check.dump

Other important recovery files are also in the directory /tmp/tmp.9696FiZ4zo
Please remove the /tmp/tmp.9696FiZ4zo directory yourself after you fixed the situation, I cannot do it for you

        Start 123: testshell_replay_ls
123/187 Test #123: testshell_replay_ls ......................   Passed    1.22 sec
        Start 124: testshell_markdown_msr_syntax
124/187 Test #124: testshell_markdown_msr_syntax ............***Failed    2.14 sec
kdb set /test/a a
kdb set /test/b b
kdb get /test/a
kdb get /test/c
kdb rm -r /test
kdb set /test/x x
kdb set /test/y y
kdb get /test/x
kdb get /test/y
kdb export /test ini
kdb ls /test
kdb rm -r /test
ls
echo test
printf 'test\nbla'
if [ -e `kdb file user` ]; then cat `kdb file user`; fi
echo `kdb file system`
ls
echo `    kdb file system`
Binärdateien /tmp/tmp.qw37yh5BAW/user.export.dump und /tmp/tmp.qw37yh5BAW/user.check.dump sind verschieden.
Test did not leave user config in the same state at is was before!
This means the test itself is flawed!
You can inspect the original user config in /tmp/tmp.qw37yh5BAW/user.export.dump
compared to situation now in /tmp/tmp.qw37yh5BAW/user.check.dump

Other important recovery files are also in the directory /tmp/tmp.qw37yh5BAW
Please remove the /tmp/tmp.qw37yh5BAW directory yourself after you fixed the situation, I cannot do it for you

        Start 125: testshell_markdown_ini_crash_test
125/187 Test #125: testshell_markdown_ini_crash_test ........   Passed    0.90 sec
        Start 126: testshell_markdown_kdb-global-umount
126/187 Test #126: testshell_markdown_kdb-global-umount .....***Failed    1.15 sec
kdb global-mount tracer
kdb global-mount
kdb global-umount tracer
kdb global-mount
kdb global-umount spec
kdb global-mount
Binärdateien /tmp/tmp.XKe6lLzJtN/system.export.dump und /tmp/tmp.XKe6lLzJtN/system.check.dump sind verschieden.
Test did not leave system config in the same state at is was before!
This means the test itself is flawed!
You can inspect the original system config in /tmp/tmp.XKe6lLzJtN/system.export.dump
compared to situation now in /tmp/tmp.XKe6lLzJtN/system.check.dump

Other important recovery files are also in the directory /tmp/tmp.XKe6lLzJtN
Please remove the /tmp/tmp.XKe6lLzJtN directory yourself after you fixed the situation, I cannot do it for you

        Start 127: testshell_markdown_readme_msr
127/187 Test #127: testshell_markdown_readme_msr ............   Passed    1.31 sec
        Start 128: testshell_markdown_issue_template
128/187 Test #128: testshell_markdown_issue_template ........   Passed    1.22 sec
        Start 129: testshell_markdown_tutorial_cascading
129/187 Test #129: testshell_markdown_tutorial_cascading ....***Failed    2.43 sec
 Sorry, 1 warning was issued ;(
 Warning (#79):
        Description: postcondition of backend was violated
        Ingroup: kdb
        Module: 
        At: /home/markus/Projekte/Elektra/current/src/libs/elektra/split.c:499
        Reason: drop key system/sw/bachmann/swmod/Priority not belonging to "/sw/bachmann/swmod" with name "/sw/bachmann/swmod" but instead to "" with name "default" because it is hidden by other mountpoint
        Mountpoint: system/elektra/modules/validation
        Configfile: 
 Sorry, 1 warning was issued ;(
 Warning (#79):
        Description: postcondition of backend was violated
        Ingroup: kdb
        Module: 
        At: /home/markus/Projekte/Elektra/current/src/libs/elektra/split.c:499
        Reason: drop key system/sw/bachmann/swmod/Priority not belonging to "/sw/bachmann/swmod" with name "/sw/bachmann/swmod" but instead to "" with name "default" because it is hidden by other mountpoint
        Mountpoint: system/elektra/modules/validation
        Configfile: 
kdb get /sw/tutorial/cascading/#0/current/test
kdb set system/sw/tutorial/cascading/#0/current/test "hello world"
kdb get /sw/tutorial/cascading/#0/current/test
kdb set user/sw/tutorial/cascading/#0/current/test "hello galaxy"
kdb get /sw/tutorial/cascading/#0/current/test
mkdir kdbtutorial
cd kdbtutorial
kdb set dir/sw/tutorial/cascading/#0/current/test "hello universe"
kdb get /sw/tutorial/cascading/#0/current/test
cd ..
kdb get /sw/tutorial/cascading/#0/current/test
kdb set system/overrides/test "hello override"
kdb setmeta spec/sw/tutorial/cascading/#0/current/test override/#0 /overrides/test
kdb get /sw/tutorial/cascading/#0/current/test
kdb set /overrides/test "hello user"
kdb get /sw/tutorial/cascading/#0/current/test
kdb rm -r user/sw/tutorial/
kdb rm -r system/sw/tutorial
kdb rm -r system/overrides/test
kdb rm /overrides/test
kdb rm -r spec/sw/tutorial/
kdb rm -f user/overrides
rm -r .dir/
rmdir kdbtutorial
Binärdateien /tmp/tmp.fxTZF6GM8x/user.export.dump und /tmp/tmp.fxTZF6GM8x/user.check.dump sind verschieden.
Test did not leave user config in the same state at is was before!
This means the test itself is flawed!
You can inspect the original user config in /tmp/tmp.fxTZF6GM8x/user.export.dump
compared to situation now in /tmp/tmp.fxTZF6GM8x/user.check.dump

Other important recovery files are also in the directory /tmp/tmp.fxTZF6GM8x
Please remove the /tmp/tmp.fxTZF6GM8x directory yourself after you fixed the situation, I cannot do it for you

        Start 130: testshell_markdown_kdb-complete
130/187 Test #130: testshell_markdown_kdb-complete ..........   Passed    2.11 sec
        Start 131: testshell_markdown_kdb-ls
131/187 Test #131: testshell_markdown_kdb-ls ................***Failed    1.99 sec
kdb set /sw/elektra/examples/kdb-ls/test val1
kdb set /sw/elektra/examples/kdb-ls/test/foo/bar val2
kdb set /sw/elektra/examples/kdb-ls/test/fizz/buzz fizzbuzz
kdb set /sw/elektra/examples/kdb-ls/tost val3
kdb set /sw/elektra/examples/kdb-ls/tost/level lvl
kdb ls /sw/elektra/examples/kdb-ls
kdb ls /sw/elektra/examples/kdb-ls/ --max-depth=1
kdb ls /sw/elektra/examples/kdb-ls --max-depth=1
kdb ls /sw/elektra/examples/kdb-ls --min-depth=1 --max-depth=2
kdb ls /sw/elektra/examples/kdb-ls/test
kdb ls /sw/elektra/examples/kdb-ls/ -v
Binärdateien /tmp/tmp.bgD8E7xK20/user.export.dump und /tmp/tmp.bgD8E7xK20/user.check.dump sind verschieden.
Test did not leave user config in the same state at is was before!
This means the test itself is flawed!
You can inspect the original user config in /tmp/tmp.bgD8E7xK20/user.export.dump
compared to situation now in /tmp/tmp.bgD8E7xK20/user.check.dump

Other important recovery files are also in the directory /tmp/tmp.bgD8E7xK20
Please remove the /tmp/tmp.bgD8E7xK20 directory yourself after you fixed the situation, I cannot do it for you

        Start 132: testshell_markdown_blockresolver
132/187 Test #132: testshell_markdown_blockresolver .........   Passed    1.49 sec
        Start 133: testshell_markdown_boolean
133/187 Test #133: testshell_markdown_boolean ...............   Passed    1.23 sec
        Start 134: testshell_markdown_csvstorage
134/187 Test #134: testshell_markdown_csvstorage ............   Passed    2.75 sec
        Start 135: testshell_markdown_cachefilter
135/187 Test #135: testshell_markdown_cachefilter ...........   Passed    0.95 sec
        Start 136: testshell_markdown_camel
136/187 Test #136: testshell_markdown_camel .................***Failed    1.35 sec
kdb mount config.yaml /examples/camel camel
kdb set /examples/camel/key value
kdb get /examples/camel/key
kdb set /examples/camel/kittens "warm & fuzzy"
kdb get /examples/camel/kittens
kdb set /examples/camel/empty ""
kdb export /examples/camel camel
kdb rm -r /examples/camel
kdb umount /examples/camel
Binärdateien /tmp/tmp.KCKyMq3K8P/mount.export.dump und /tmp/tmp.KCKyMq3K8P/mount.check.dump sind verschieden.
Test did not leave mount config in the same state at is was before!
This means the test itself is flawed!
You can inspect the original mount config in /tmp/tmp.KCKyMq3K8P/mount.export.dump
compared to situation now in /tmp/tmp.KCKyMq3K8P/mount.check.dump

Other important recovery files are also in the directory /tmp/tmp.KCKyMq3K8P
Please remove the /tmp/tmp.KCKyMq3K8P directory yourself after you fixed the situation, I cannot do it for you

        Start 137: testshell_markdown_conditionals
137/187 Test #137: testshell_markdown_conditionals ..........***Failed    2.26 sec
kdb mount conditionals.dump /examples/conditionals conditionals dump
kdb set /examples/conditionals/fkey 3.0
kdb set /examples/conditionals/hkey hello
kdb setmeta user/examples/conditionals/key check/condition "(../hkey == 'hello') ? (../fkey == '3.0')"
kdb setmeta user/examples/conditionals/key check/condition "(../hkey == 'hello') ? (../fkey == '5.0')"
kdb set user/examples/conditionals/hkey Hello
kdb setmeta user/examples/conditionals/hkey assign/condition "(./ == 'Hello') ? ('World')"
kdb get user/examples/conditionals/hkey
kdb rm -r /examples/conditionals
kdb umount /examples/conditionals
kdb mount main.ini /examples/conditionals ni
kdb mount sub.ini /examples/conditionals/sub ini
kdb global-mount conditionals || $(exit 0)
echo 'key1 = val1'                                                     >  `kdb file /examples/conditionals`
echo '[key1]'                                                          >> `kdb file /examples/conditionals`
echo "check/condition = (./ == 'val1') ? (../sub/key == 'true')" >> `kdb file /examples/conditionals`
echo "key = false" > `kdb file /examples/conditionals/sub`
kdb export /examples/conditionals ini
kdb set /examples/conditionals/sub/key true
kdb export /examples/conditionals ini
kdb rm -r /examples/conditionals
kdb umount /examples/conditionals/sub
kdb umount /examples/conditionals
kdb global-umount conditionals
Binärdateien /tmp/tmp.3TDCSJdg9v/system.export.dump und /tmp/tmp.3TDCSJdg9v/system.check.dump sind verschieden.
Test did not leave system config in the same state at is was before!
This means the test itself is flawed!
You can inspect the original system config in /tmp/tmp.3TDCSJdg9v/system.export.dump
compared to situation now in /tmp/tmp.3TDCSJdg9v/system.check.dump

Other important recovery files are also in the directory /tmp/tmp.3TDCSJdg9v
Please remove the /tmp/tmp.3TDCSJdg9v directory yourself after you fixed the situation, I cannot do it for you

        Start 138: testshell_markdown_dini
138/187 Test #138: testshell_markdown_dini ..................   Passed    1.50 sec

187/187 Test #187: testkdb_simple ...........................   Passed    1.59 sec

96% tests passed, 7 tests failed out of 187

Label Time Summary:
bindings    =   0.64 sec (9 tests)
kdbtests    = 130.45 sec (73 tests)
memleak     = 126.14 sec (77 tests)

Total Test time (real) = 133.35 sec

The following tests FAILED:
        122 - testshell_mathcheck (Failed)
        124 - testshell_markdown_msr_syntax (Failed)
        126 - testshell_markdown_kdb-global-umount (Failed)
        129 - testshell_markdown_tutorial_cascading (Failed)
        131 - testshell_markdown_kdb-ls (Failed)
        136 - testshell_markdown_camel (Failed)
        137 - testshell_markdown_conditionals (Failed)
Errors while running CTest

[markus2330]

Cannot reproduce it now, seems to be a local problem or actually a result of many tests not prefixed with /tests #1820 and thus quite error prone if any test has left-overs.