Closed gdalle closed 1 year ago
@BatyLeo the tests of your general imitation loss are commented out
Patch coverage: 100.00
% and project coverage change: -11.32
:warning:
Comparison is base (
464508c
) 93.71% compared to head (74c2379
) 82.39%.
:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.
@gdalle ImitationLoss
tests are updated
Should we remove/disable nightly from CI (and add 1.8) before merging ?
Should we remove/disable nightly from CI (and add 1.8) before merging ?
What I usually see in CI setups is that people test on
I don't think we need to cover all versions in between. As for the bug on nightly, it's getting fixed soon: https://github.com/FluxML/Zygote.jl/pull/1420
The better option would be to ignore nightly for the badge. I opened a topic here (https://discourse.julialang.org/t/ignoring-nightly-failure-for-ci-badge/98028) but the solution I adopted doesn't seem to work anymore so :shrug:
Replace the usual tests with the new testitem framework for VSCode. This allows tests to be run independently and in parallel.
Solves #46
By the way, I think we can still see the plots: there is a button "Show output" at the top of the testing tab