New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

testshell: fails #1704

Open
markus2330 opened this Issue Nov 19, 2017 · 0 comments

Comments

Projects
None yet
1 participant
@markus2330
Contributor

markus2330 commented Nov 19, 2017

Might be a local problem but to have it documented:

        Start 136: testshell_markdown_kdb-global-umount
136/194 Test #136: testshell_markdown_kdb-global-umount .....***Failed    0.28 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.bFVSN0gsAu/system.export.dump und /tmp/tmp.bFVSN0gsAu/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.bFVSN0gsAu/system.export.dump
compared to situation now in /tmp/tmp.bFVSN0gsAu/system.check.dump

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




146/194 Test #146: testshell_markdown_conditionals ..........***Failed    0.77 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.k6GTkDqtAw/system.export.dump und /tmp/tmp.k6GTkDqtAw/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.k6GTkDqtAw/system.export.dump
compared to situation now in /tmp/tmp.k6GTkDqtAw/system.check.dump

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

        Start 147: testshell_markdown_enum
147/194 Test #147: testshell_markdown_enum ..................   Passed    0.51 sec
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment