commit | 7e0e7174f95ccb86f90a279a6f72c5a8c3cf9b0d | [log] [tgz] |
---|---|---|
author | Rohit Makasana <rohitbm@chromium.org> | Fri Mar 30 00:08:51 2018 |
committer | chrome-bot <chrome-bot@chromium.org> | Fri Mar 30 20:40:49 2018 |
tree | fe0c118ca891d6ba4fda1bb36238503bd90ca359 | |
parent | ee9c06565b978af1a85e33200c41acb734503614 [diff] |
Enable arc-cts-follower test suite in the test lab. TEST=None BUG=b:64079026 CQ-DEPEND=CL:*597966 Change-Id: Ic3098f7771f9a866110e30c291726ad3b33b5f13 Reviewed-on: https://chromium-review.googlesource.com/987241 Commit-Ready: Rohit Makasana <rohitbm@chromium.org> Tested-by: Ilja H. Friedel <ihf@chromium.org> Reviewed-by: Po-Hsien Wang <pwang@chromium.org> Reviewed-by: Ilja H. Friedel <ihf@chromium.org>
Put your Google gCloud SDK to ~/google-cloud-sdk
.
Install App Engine SDK to ~/google-cloud-sdk
:
~/google-cloud-sdk/bin/gcloud components install app-engine-python
Run python setup_environment.py
to download third-party libraries and credentials.
Failed to install third-packages in requirement.txt:
Workround: Run pip install -t lib -r requirements.txt
locally on your workstation to verify whether it could work.
Failed to download credentials from ‘gs://suite-scheduler.google.com.a.appspot.com/credentials/’:
Workround: Run gsutil ls gs://suite-scheduler.google.com.a.appspot.com/credentials/
locally on your workstation to verify whether you can fetch credentials with gsutil.
If there's any auth issue, it may be because
a. You‘re not using your corp account to login gcloud. Please run gcloud auth list
to check what’s the used account for gcloud.
b. Your corp account is not whitelisted by suite-scheduler project. Please contact @xixuan to whitelist your ldap.
Presubmit will kick off sanity test for verifying suite_scheduler.ini:
python runner.py --test_type sanity
Run unittest:
python runner.py' or 'python runner.py --test_type unittest
Run integration test:
python runner.py --test_type integration
Run tests with debug mode:
python runner.py --debug