ci: Use trace logging in integration tests
It's helpful to have all the details when debugging issues.
@@ -63,7 +63,7 @@ steps:
- bazel build //:scion //:scion-ci >/dev/null 2>&1
- tar -kxf bazel-bin/scion.tar -C bin --overwrite
- tar -kxf bazel-bin/scion-ci.tar -C bin --overwrite
- - ./scion.sh topology
+ - ./scion.sh topology -t
- ./scion.sh run && sleep 10
- ./bin/end2end_integration -log.console warn
- ./integration/revocation_test.sh
@@ -79,7 +79,7 @@ steps:
- bazel build //:scion //:scion-ci >/dev/null 2>&1
- tar -kxf bazel-bin/scion.tar -C bin --overwrite
- tar -kxf bazel-bin/scion-ci.tar -C bin --overwrite
- - ./scion.sh topology
+ - ./scion.sh topology -t
- ./scion.sh run && sleep 10
- ./bin/cert_req_integration -log.console warn
- ./bin/pp_integration -log.console warn
@@ -98,7 +98,7 @@ steps:
- bazel build //:scion //:scion-ci >/dev/null 2>&1
- tar -kxf bazel-bin/scion.tar -C bin --overwrite
- tar -kxf bazel-bin/scion-ci.tar -C bin --overwrite
- - ./scion.sh topology --monolith
+ - ./scion.sh topology -t --monolith
- ./scion.sh run && sleep 10
- ./bin/end2end_integration -log.console warn
artifact_paths:
