tools/configure_for_func_testing.sh is advised (as described above).
When running full-stack tests on a clean VM for the first time, we
advise to run ./stack.sh successfully to make sure all Neutron's
-dependencies are met. Also note that in order to preserve resources
-on the gate, running the dsvm-functional suite will also run all
-full-stack tests (and a new worker won't be assigned specifically for
-dsvm-fullstack). Full-stack based Neutron daemons produce logs to a
+dependencies are met. Full-stack based Neutron daemons produce logs to a
sub-folder in /tmp/fullstack-logs (for example, a test named
"test_example" will produce logs to /tmp/fullstack-logs/test_example/),
so that will be a good place to look if your test is failing.
VENV=${1:-"dsvm-functional"}
-if [ "$VENV" == "dsvm-functional" ]
+if [ "$VENV" == "dsvm-functional" ] || [ "$VENV" == "dsvm-fullstack" ]
then
# The following need to be set before sourcing
# configure_for_func_testing.
# holding those files to /opt/stack/logs. Files with .log suffix have their
# suffix changed to .txt (so browsers will know to open the compressed
# files and not download them).
- if [ -d /tmp/fullstack-logs/ ]; then
+ if [ "$venv" == "dsvm-fullstack" ] && [ -d /tmp/fullstack-logs/ ]; then
sudo find /tmp/fullstack-logs -iname "*.log" -type f -exec mv {} {}.txt \; -exec gzip -9 {}.txt \;
sudo mv /tmp/fullstack-logs/* /opt/stack/logs/
fi
}
-if [ "$venv" == "dsvm-functional" ]
+if [ "$venv" == "dsvm-functional" ] || [ "$venv" == "dsvm-fullstack" ]
then
owner=stack
sudo_env=
target_dirs = [
this_dir,
os.path.join(parent_dir, 'retargetable'),
- os.path.join(parent_dir, 'fullstack'),
]
for start_dir in target_dirs:
new_tests = loader.discover(start_dir=start_dir, pattern=pattern)