THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Note: Sometimes your may get a messed up terminal after data loading, e.g. not displaying any typed in characters or carriage return. In this case, type ctrl+c, then type "stty sane", then press enter to recover.
...
| Code Block | ||
|---|---|---|
| ||
# For the back-end tests, the Impala cluster must not be running: ./bin/start-impala-cluster.py --kill ./bin/run-backend-tests.sh # or ctest # To run just one test (and show what broke) (make sure to source ./bin/set-classpath.sh first): ctest --output-on-failure -R expr-test # You can also run just a single test at a time. If this fails, be sure # that you've run set-classpath.sh before-hand. # You can then use command line parameters to run a subset of tests: # To get help with parameters: be/build/latest/runtime/mem-pool-test --help # To run just one test within a test: be/build/latest/runtime/mem-pool-test --gtest_filter=MemPoolTest.TryAllocateAligned |
Run just JavaScript tests (webUI pages)
| Code Block | ||
|---|---|---|
| ||
# To run JavaScript tests using JEST for the webUI pages
./tests/run-js-tests.sh |
Run most end-to-end tests (but not custom cluster tests)
...
To make things even more complicated, there's bin/run-all-tests.sh, which invokes run-tests.py (but also "mvn test" and the C++ tests), and buildall.sh, which invokes run-all-tests.sh.
Troubleshooting
1. Test failures due to missing libTestUdfs.so
| Code Block |
|---|
E MESSAGE: AnalysisException: Could not load binary: /test-warehouse/libTestUdfs.so
E Failed to get file info hdfs://localhost:20500/test-warehouse/libTestUdfs.so
E Error(2): No such file or directory |
That file is created and uploaded by testdata/bin/copy-udfs-udas.sh. You can try
| Code Block |
|---|
testdata/bin/copy-udfs-udas.sh -build |