[ABANDONED] draft of DRIFT region tag tracking#4402
Conversation
| EXIT=$? | ||
|
|
||
| # Inject region tag data into the test log | ||
| REGION_TAG_PARSER_DIR="$PARENT_DIR/region-tag-parser" |
There was a problem hiding this comment.
Can you use a temporary directory? Also it's great if you make sure the temporary directory will be deleted after the test.
There was a problem hiding this comment.
Update: maybe you can just install them in /opt or somewhere then it will only exists in the container.
/tmp is shared between the container and the host for a reason, so it's probably better to use somewhere else.
|
FYI - this is a draft PR. (No review necessary until I actually get this
working. 🙂 )
|
2d097ee to
392f8b1
Compare
|
FYI, you can run the whole test locally. Here is an example for running lint full build: $ cd python-docs-samples
$ TRAMPOLINE_BUILD_FILE=.kokoro/tests/run_tests.sh RUN_TESTS_SESSION=lint .kokoro/trampoline_v2.shFor python sessions, you probably want to have secrets locally: $ cd python-docs-samples
$ scripts/decrypt-secrets.sh # You need permission of course
$ TRAMPOLINE_BUILD_FILE=.kokoro/tests/run_tests.sh RUN_TESTS_SESSION=py-3.7 .kokoro/trampoline_v2.shIf you want to use your own Cloud projects: $ cd python-docs-samples
$ cp testing/test-env.tmpl.sh testing/test-env.sh # and edit it
$ cp /some/where/your-service-account-json.key testing/service-account.json
$ TRAMPOLINE_BUILD_FILE=.kokoro/tests/run_tests.sh RUN_TESTS_SESSION=py-3.7 .kokoro/trampoline_v2.shThis way, it will run the tests in an identical way as on Kokoro builds, so you can develop it locally without pushing any changes. |
|
@tmatsuo thanks! I think this needs to be run on Kokoro itself though, as part of what I'm testing is the ability to export these test results (which I think happens outside the immediate build context). |
|
Closing in favor of #4506 |
No description provided.