| commit | 08bb5589019bbaae1039240ce347cdc3ed05f43a | [log] [tgz] |
|---|---|---|
| author | Dhanya Ganesh <dhanyaganesh@chromium.org> | Tue Dec 04 23:22:14 2018 |
| committer | chrome-bot <chrome-bot@chromium.org> | Fri Dec 07 06:06:45 2018 |
| tree | 21801873f9d0d7d1f58d3bab7ae5c700674e370a | |
| parent | 56ec0b899621c5e58670e3efeafa99143ae9881a [diff] |
README: Notice of function removal Chromite has removed functions used exclusively by this project. BUG=chromium:905751 TEST=na Change-Id: I0c10827fe81a4e9b0f0b46140b7f0cdb4de02dd8 Reviewed-on: https://chromium-review.googlesource.com/1361943 Commit-Ready: Dhanya Ganesh <dhanyaganesh@chromium.org> Tested-by: Dhanya Ganesh <dhanyaganesh@chromium.org> Reviewed-by: Jason Clinton <jclinton@chromium.org>
https://chromium.googlesource.com/chromiumos/infra/bad_cl_detector
As of Dec 2018, the underlying database calls in this repository are no longer supported in Chromite.
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