Branch | Total Compute Hours | Percentage |
---|---|---|
total | 128074 | 100.0 |
autoland | 70304 | 54.9 |
mozilla-inbound | 33290 | 26.0 |
mozilla-central | 24480 | 19.1 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
{ | |
"<config A>" : { | |
"total": "<num tests: int>", | |
"skipped": [ | |
"<test 1>", | |
"<test 2>", | |
"..." | |
], | |
}, | |
"<config B>": "..." |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
diff --git a/adr/recipes/intermittent_tests.py b/adr/recipes/intermittent_tests.py | |
index ff4b3fe..ffbb0a3 100644 | |
--- a/adr/recipes/intermittent_tests.py | |
+++ b/adr/recipes/intermittent_tests.py | |
@@ -2,36 +2,33 @@ | |
This is currently broken. | |
.. code-block:: bash | |
adr intermittent_tests |
Branch | Total Compute Hours | Percentage |
---|---|---|
total | 422461 | 100.0 |
autoland | 203398 | 48.1 |
mozilla-inbound | 126464 | 29.9 |
mozilla-central | 92599 | 21.9 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
try_usage: | |
recipe: try_usage | |
from: now-week | |
to: now | |
try_usage: | |
command: | |
adr try_usage --from now-week --to now |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Poetry | |
====== | |
* Version: 0.12.11 | |
* Python: 3.6.8 | |
Virtualenv | |
========== |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
diff --git a/tools/lint/license.yml b/tools/lint/license.yml | |
--- a/tools/lint/license.yml | |
+++ b/tools/lint/license.yml | |
@@ -1,28 +1,44 @@ | |
--- | |
license: | |
description: License Check | |
include: | |
- . | |
exclude: |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Traceback (most recent call last): | |
File "/home/ahal/dev/mozilla-central/python/mozlint/mozlint/roller.py", line 39, in _run_worker | |
res = func(paths, config, **lintargs) or [] | |
File "/home/ahal/dev/mozilla-central/python/mozlint/mozlint/types.py", line 50, in __call__ | |
return self._lint(paths, config, **lintargs) | |
File "/home/ahal/dev/mozilla-central/python/mozlint/mozlint/types.py", line 134, in _lint | |
return func(files, config, **lintargs) | |
File "/home/ahal/dev/mozilla-central/tools/lint/rst/__init__.py", line 100, in lint | |
filename, lineno, error, level, message = parse_with_split(errors) | |
File "/home/ahal/dev/mozilla-central/tools/lint/rst/__init__.py", line 65, in parse_with_split |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
diff --git a/tools/lint/docs/usage.rst b/tools/lint/docs/usage.rst | |
--- a/tools/lint/docs/usage.rst | |
+++ b/tools/lint/docs/usage.rst | |
@@ -1,14 +1,28 @@ | |
Running Linters Locally | |
======================= | |
Using the Command Line | |
---------------------- | |
It's late and I'm tired, but I was lying in bed thinking about test scheduling (yeah, yeah), and had a moment of clarity. This is my attempt to write my thoughts down before falling asleep and losing them all.
We've been trying to think of ways to integrate code coverage into our scheduling algorithms somehow. The problem is that we don't have a reliable way of mapping test paths to chunks. Chunks vary by platform and even within the same platform tests can move around between chunks from one push to another. My realization is that to date we have been thinking of code coverage (or machine learning) reduction as something that happens during the optimization phase. Here are the full set of