CircleCI coverage #3267
CircleCI coverage #3267
Conversation
jomuel
force-pushed
the
issue-3072
branch
28 times, most recently
from
0e8c72e to
3637667
Compare
jomuel
force-pushed
the
issue-3072
branch
10 times, most recently
from
5ad6c1a to
70aa666
Compare
Codecov Report
@@ Coverage Diff @@
## master #3267 +/- ##
=========================================
Coverage ? 74.81%
=========================================
Files ? 94
Lines ? 12150
Branches ? 1689
=========================================
Hits ? 9090
Misses ? 2443
Partials ? 617Continue to review full report at Codecov.
|
jomuel
force-pushed
the
issue-3072
branch
2 times, most recently
from
22417a0 to
6b74c51
Compare
| @@ -473,6 +487,15 @@ workflows: | |||
| - prepare-python-3.6 | |||
| - build-synapse | |||
|
|
|||
| - test: | |||
| name: test-fuzz-3.6 | |||
There was a problem hiding this comment.
Both this and test-fuzz-3.7 needs to be referenced in the requires section of the finalize step in the workflow definitions.
There was a problem hiding this comment.
Done, I added the fuzz tests to the nightly build too.
| @@ -551,6 +574,15 @@ workflows: | |||
| - prepare-python-3.7 | |||
| - build-synapse | |||
|
|
|||
| - test: | |||
| name: test-fuzz-3.7 | |||
| << *job-template-test | ||
| env: | ||
| - TEST='raiden/tests/fuzz' | ||
| - TRANSPORT_OPTIONS='--hypothesis-show-statistics' |
There was a problem hiding this comment.
Hm not the cleanest way to 'abuse' the TRANSPORT_OPTIONS here but I guess since travis is on the way out in any case it doesn't matter that much.
There was a problem hiding this comment.
That's what I thought, otherwise I would have renamed them to ADDITIONAL_OPTIONS or something.
jomuel
force-pushed
the
issue-3072
branch
4 times, most recently
from
bb706ae to
75b507f
Compare
coverageon all testsMerge this after #3172, which should fix performance issues when testing with matrix. Builds using
coverageare somewhat flaky at the moment since the integration tests with matrix transport sometimes time out.Closes #3071