| commit | 7d37b043cf72c2f94f1a20aa8325830615817b2d | [log] [tgz] |
|---|---|---|
| author | Andrew Lamb <andrewlamb@chromium.org> | Mon Sep 21 16:25:41 2020 |
| committer | Andrew Lamb <andrewlamb@chromium.org> | Mon Sep 21 16:27:48 2020 |
| tree | 624c98f8652c68c4e5b553cf83ecb4f9425c7b70 | |
| parent | 08bb5589019bbaae1039240ce347cdc3ed05f43a [diff] |
bad_cl_detector: Delete. - Contains uninclusive language, see go/chromium-project-code-inclusion and BUG. Need to leave repo in place because branched manifests reference it. BUG=chromium:1119243 TEST=None Change-Id: Id4c17677416a860de93bbd7253a33fde0b20524a
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.
As of Sep 2020 the code in this repo was deleted because it contains uninclusive language. See go/chromium-project-code-inclusion and crbug.com/1119243. The repo is left unarchived because some branched manifests reference it.
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