| commit | 56ec0b899621c5e58670e3efeafa99143ae9881a | [log] [tgz] |
|---|---|---|
| author | David Burger <dburger@chromium.org> | Wed Nov 21 21:15:15 2018 |
| committer | chrome-bot <chrome-bot@chromium.org> | Fri Nov 30 00:08:59 2018 |
| tree | 43277a9ee02afb90dc81f1d9cf891a9c791fe1db | |
| parent | a6bade48153992dc3d91697c45db9d36231e3bfc [diff] |
Remove waterfall parameter from InsertBuild calls in tests Per the change in http://crrev.com/c/1347298 remove the waterfall parameter from calls to InsertBuild. TEST=cros tryjob -g "1347298 1347299 1347393 1347392 1347391" chromeos-infra-unittests-pre-cq BUG=chromium:836551 CQ-DEPEND=CL:1347298 Change-Id: I95b21f53bd43da87f15812e04f012e02b506d8f2 Reviewed-on: https://chromium-review.googlesource.com/1347391 Commit-Ready: David Burger <dburger@chromium.org> Tested-by: David Burger <dburger@chromium.org> Reviewed-by: Jason Clinton <jclinton@chromium.org> Reviewed-by: Don Garrett <dgarrett@chromium.org>
https://chromium.googlesource.com/chromiumos/infra/bad_cl_detector
A system to detect if a given build failure is caused by bad CL.
The virtualenv for this project is managed with pipenv. If you don't already have pipenv installed, you can install it with “pip install pipenv”.
Then run:
deactivate # make sure you are not already in a virtualenv pipenv --two install protoc -I=lib/protos --python_out=lib/protos
You can fetch cidb credentials with “cros cidbcreds”. You will need to pass in the db credentials' path to the script.
Downloading training data, training a model and cross validating is done by one script:
pipenv run python lib/bad_cl_detector_driver.py --cred-dir=$CRED_DIR
Or, you can enter a virtualenv shell with “pipenv shell”, and then just run python lib/.
Currently this requires word2vec and word2int files to work. Making this self-contained is a work in progress.
Tests are run with pytest:
pipenv run pytest