| commit | c3d4050dd2fbbddf664f7a8bb9109aaed79ee78c | [log] [tgz] |
|---|---|---|
| author | Aadit Modi <modia@google.com> | Wed Jun 17 17:55:40 2020 |
| committer | Aadit Modi <modia@google.com> | Wed Jun 17 17:55:40 2020 |
| tree | 9a33fdf0bcefc826bf7bc11056d47b1bec2bd6c3 | |
| parent | 7668ae86fc47a3cfba40dc7675bb4656422799b5 [diff] |
Remove board-list from pool:faft-cr50 Deleting entries of the DUT board names from the suite: faft_cr50_prepvt,faft_cr50_pvt, so we can overcome the board list dependency. BUG=chromium:1095731 Test=None Change-Id: I35fa70ae99c6a61f0183ac94b8812d65c8be06ea
Due to https://crbug.com/792690, this must be run outside the chroot.
Install Google Cloud SDK:
Log in to gcloud: gcloud auth login LDAP@google.com
Install pip:
sudo apt-get install python-pip
If you only modify the files in configs/, run:
python setup_environment.py --load_infra_libs
to download the dependencies. Otherwise, load the credentials (need permission from CrOS Test Platform team) to conduct the unit and integration tests:
python setup_environment.py --load_infra_libs --load_cred
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 @lxn to whitelist your ldap.
Run sanity test for config changes:
python runner.py --test_type sanity
Run unittest and integration for any changes in production code:
python runner.py --test_type unittest python runner.py --test_type integration
Run tests with debug mode:
python runner.py --debug
Run suite scheduler v2 as a local development server:
If you want to verify any APIs locally, you can run suite scheduler v2 as a local development server (https://cloud.google.com/appengine/docs/standard/python/tools/using-local-server):
a. Finally, start dev_appserver.py in a window:
dev_appserver.py app.yaml \
--port=8888 \
--admin_port=8001 \
--log_level=debug
b. Test it:
curl 'http://localhost:8888/cron/trigger_event', or open it in chrome.
Please note that once a dev_appserver is started, it simulates data_store & task_queue, which means:
a. The datastore doesn‘t contain any previous cron run’s information, so the first round of cron/trigger_event won't trigger any event.
b. The task queue is newly created with 0 tasks in it unless cron/trigger_event adds tasks in it. Dev_appserver restart will cause the local task queue to get purged.
Add or update your job configuration in configs/suite_scheduler.ini.
Update configs/lab_config.ini, if the suite test relies on new board or model. Note, suite scheduler does not automatically catch the new boards or models added to the lab.
Run python runner.py --test_type sanity to ensure config is eligible.
Submit the change and ping/file bug to infra team. Test platform deputy will rollout your change to the production. Once this is done, you may find the scheduling status of the new suite via our dashboard.