Uh oh!
There was an error while loading. Please reload this page.
Conversation
…est to perform with the user
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Codecov Report
@@ Coverage Diff @@## develop #620 +/- ##
===========================================
+ Coverage 89.59% 89.88% +0.29%
===========================================
Files 32 32 Lines 3123 3193 +70 ===========================================
+ Hits 2798 2870 +72 + Misses 325 323 -2
Continue to review full report at Codecov.
|
mfeurer
commented
Feb 20, 2019
Looks good to me. Except that one line which basically says to not merge this PR. |
mfeurer
commented
Feb 20, 2019
And it seems there are some minor flake8 errors in the push test. I really don't know what to do with the flake8 errors in the PR test as they are so many and would only happen after the merge. |
janvanrijn
commented
Feb 20, 2019
we need to wait for the PHP PR to be merged.
Bigger issue: some lines are OK, other still contain mistakes (legacy mistakes, and we don't really want to solve them all at once) Clearly it would be beneficial to have the whole project flake compatible. We can maybe ask the programmer to do so on one of the first days? (Once all big PR's are merged) From there on flake can run on all lines, not just the diff, and we don't have these problems anymore. The problems introduced in this PR will be fixed by me. |
janvanrijn
commented
Feb 21, 2019
flake8 residuals. this is fine right? Can we inform it that this warning in |
| # engine is behind. | ||
| # TODO: mock this? We have the arff already on the server | ||
| self._wait_for_processed_run(run.run_id, 200) | ||
| print(run.run_id) |
There was a problem hiding this comment.
Could you please remove this call to the print function?
mfeurer
commented
Feb 22, 2019
Looks good to me except for the failing unit tests. |
Reference Issue
What does this PR implement/fix? Explain your changes.
How should this PR be tested?
Any other comments?