Assures consistent formatting of our python codebase without having
to rely on humans to do it, or to debate during reviews.
Change-Id: I1e62cc755fa60e453dea865f436241ecae330771
Includes removal of file pattern from pep8 job which prevented
it from running on most changes. Linters will use multiple tools
and a pattern would make it fail to spot errors.
This check should run even if no files are changed, so it would
be able to check commit messages.
There are no real load implications because linters check is
just a simple tox execution which has minimal resource requirements.
Includes reactivaction or linting which was not running on
the entire repository. This required few minor fixes.
Partial-Bug: #1786286
Change-Id: I4d4279309af55c2663e98bd0cdec9224f03c1fa0
Currently it ignores failure events and reports those resources as
still in progress. That's not really true, so let's report how long
it took for the resource to fail. In some cases that may be useful
information too.
Change-Id: I3eeb6a6a589574cbd556e4ce712e2454c3aec3c9
The event list output has appended a Z to the timestamp recently, so
we need to handle both formats now.
Change-Id: I4efe273c3f528eefbde05f6d47e7513361a95504
This way we can track how they change over time, in addition to
seeing how they behave in a single run.
Change-Id: I28618906e119ad22d10d087e2faf75337849cb74
Looking through our graphite metrics, by far the longest time is
spent deploying the overcloud. This change allows us to collect
more granular data about what is using that time in the deployment.
At some point we may want to add this to the graphite data so we
can track it over time, but just making it available in the postci
logs is a good first step.
Change-Id: Ibae0f6259146dc0da73d43aba0ff31a24ae71eff