Wireshark-bugs: [Wireshark-bugs] [Bug 9174] [PATCH] Fix test suite, add TLS 1.2 test suites with
Comment # 14
on bug 9174
from Peter Wu
(In reply to comment #13)
> Comment on attachment 11625 [details]
> [PATCH 1/5] tests: support out-of-source-tree tests
>
> This is broken for me:
>
> - when I run from within the "test" directory I get
> 1 Suite: TShark file I/O
> 1.1 Step: Input file
> "Input file" Failed!
> exit status of ../tshark: 127
> ./testout.txt:suite-io.sh: line 37: ../tshark: No such file or directory
This is why I made WS_BIN_PATH override-able, otherwise the test will always
fail on a clean source tree.
> - when I run from the main checkout directory I get
> ./test/test.sh: line 65: test-backend.sh: No such file or directory
> ./test/test.sh: line 67: config.sh: No such file or directory
> ./test/test.sh: line 68: suite-clopts.sh: No such file or directory
> ./test/test.sh: line 69: suite-io.sh: No such file or directory
> ./test/test.sh: line 70: suite-capture.sh: No such file or directory
> ./test/test.sh: line 71: suite-unittests.sh: No such file or directory
> ./test/test.sh: line 72: suite-fileformats.sh: No such file or directory
> ./test/test.sh: line 73: suite-decryption.sh: No such file or directory
> ./test/test.sh: line 74: suite-nameres.sh: No such file or directory
> ./test/test.sh: line 146: test_set_output: command not found
>
> I've double-checked that my tshark binary exists in the right place still.
By "out-of-tree" I referred to the temporary files created by the tests, not
the tests themselves. For the tests themselves to run, you must still cd to the
test directory.
> Do the other patches depend on this one heavily?
Not really, but please note the above comments. If it was broken before, it
still broken now. This patch allows the tests to be run in a read-only source
tree.
Please re-consider for application.
You are receiving this mail because:
- You are watching all bug changes.
