d894c249d3
As we can't tell whether they would have passed or failed, we should consider them as if they didn't run (indeed, they didn't). First step for #166 |
||
|---|---|---|
| docs | ||
| mozci | ||
| tests | ||
| .flake8 | ||
| .gitignore | ||
| .isort.cfg | ||
| .pre-commit-config.yaml | ||
| .travis.yml | ||
| LICENSE | ||
| README.md | ||
| poetry.lock | ||
| pyproject.toml | ||
| requirements.readthedocs.txt | ||
| tox.ini | ||
README.md
mozci
A library for inspecting push and task results in Mozilla's CI.
Installation
To install, run:
$ pip install mozci
Usage
Basic usage is to instantiate a Push object then start accessing properties and call methods.
For example:
from mozci.push import Push
push = Push("79041cab0cc2", branch="autoland")
print("\n".join([t.label for t in push.tasks if t.failed])
This will print all the failing tasks from a given push. See the documentation for more usage details and API docs.
Contributing
Mozci uses poetry to manage the project. So first make sure that is installed. Then clone the repo and run:
$ poetry install
This will create a virtualenv and install both project and dev dependencies in it. See the poetry documentation to learn how to work within the project.
To execute tests and linters, run:
$ tox
This should run successfully prior to submitting PRs (unless you need help figuring out the problem).
There are also some integration tests that will hit live data sources. These are run in a cron task and are excluded from the default test run. But if needed, you can run them locally via:
$ tox -e integration