changed: using the new juliaci.yml workflow for test items - #431
Open
franckgaga wants to merge 33 commits into
Open
changed: using the new juliaci.yml workflow for test items#431franckgaga wants to merge 33 commits into
juliaci.yml workflow for test items#431franckgaga wants to merge 33 commits into
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #431 +/- ##
==========================================
- Coverage 98.39% 97.09% -1.30%
==========================================
Files 29 27 -2
Lines 6353 6270 -83
==========================================
- Hits 6251 6088 -163
- Misses 102 182 +80
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Not worth it, too niche.
franckgaga
changed the title
juliaci.yml workflowjuliaci.yml workflow for test items
To avoid 1200 s timouts
The univariate syntax of `@operator` is impossible for MHE
There is a bug in DAQP.jl on x86. I can add a `skip` option on x86, but the skip option is not released yet.
90% sure that it was reading un-initialized values in the `gc` vector when `Nk < He`.
It seems, one of my test timeout even if it all passes.
Since the CI is now also there.
Benchmark Results (Julia v1)Time benchmarks
Memory benchmarks
|
Member
Author
|
CrossRef for the weird pass but still fail with timeout bug : julia-testitems/TestItemControllers.jl#76 |
Results on summary instead of comments does not seems to work
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The main advantages IMO are the "no boilerplate code" in the
ymlfile and the builtin parallelism.See here for info: https://discourse.julialang.org/t/two-years-of-test-item-framework-updates/138792#p-643953-test-items-in-ci-5
The complete documentation is here: https://julia-testitems.org/guide/ci