-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use source-based code coverage #132
Conversation
…own workflow (triggered more rarely)
Codecov Report
@@ Coverage Diff @@
## master #132 +/- ##
==========================================
+ Coverage 67.80% 70.64% +2.83%
==========================================
Files 101 90 -11
Lines 15433 15865 +432
==========================================
+ Hits 10465 11208 +743
+ Misses 4968 4657 -311
Continue to review full report at Codecov.
|
Argh, it keeps failing without giving me an error message. I think it's running out of disk space, but I can't be sure. Anyone got any ideas? |
Will it fail if a test case fails? You can try removing my flaky annoying test case that I only added the ignore flag to. Either comment out the code or remove it entirely, I'll have to redo it somehow. I've got #130 open for it. kompact/core/tests/dispatch_integration_tests.rs Line 1070 in 84be104
|
Yes...but I don't think that's the issue. But I'm sufficiently out of ideas to try it anyway :D |
Nope...wasn't it :( |
I kept the actions tab open while it was running and this is the tail end of the logging for the failing "Run tests" step:
But more importantly it fails after 59m and 59s which is probably not a coincidence? |
Coincidence...hm, not sure. Yes it always fails pretty much there. But we shouldn't be hitting the time limit. It's 6h per job, not 1h, according to the docs. It might simply be that this is the time it takes to fill some other quota. But I still don't know what causes the issue. I'm wondering if we should file a bug report for GHA. There just isn't enough output to figure out what's going wrong and the logs bloody disappear after every run -.- |
Okay it's definitely the disk space usage. The logs fail to upload because of it. Did we try max_level_error for all the test runs? |
I'm trying that now. But I guess the actual space hogger is the profiling data, which we, of course, don't want to reduce :D |
Yeah, it didn't help...I guess if the GHA runners don't have enough space to store our profiling information, we just can't do this right now. The only way to fix it would be to have it run our own runner, where we control amount of disk space. @segeljakt Have you done this by now for your CI? If yes, would be feasible to run just our code-coverage there as well? |
@Bathtor The runner is in a docker container so I can setup a second container for your runner if you would like. I am not sure how you want it configured, do you want some software to be pre-installed or does everything come with the GitHub actions YAML file? |
That would be great! |
Run Codecov job on self-hosted
Okay everything is good to me like this. The test-coverage is triggered on PR's the same way the rest of the CI is. I've commented out one test case that was dependent on the host system not running the tests with sudo privilege (which I've found unsound for a long time anyway). The Codecov comment above is a bit weird due to it being edited by codecov rather than it posting a new comment. I think it will be better with future PR's. If you're satisfied with the CI now Lars we can squash and merge this? |
pull_request: | ||
branches: | ||
- master | ||
types: [opened, reopened, synchronize] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we really want this to run with every single commit added to a PR? It's a 1h test suite. It'll take up a lot of resources on Klas' node.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It takes 13min on Klas machine 😃
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Whooot?!?
.shutdown() | ||
.expect("Kompact didn't shut down properly"); | ||
} | ||
// #[test] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you want to merge it with this test commented out? I kinda just did that as testy thingy to see if it helped to run it on GHA...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah it's too flaky. I'm gonna replace it with a better test with my next PR.
Please make sure these boxes are checked, before submitting a new PR.
You ranrustfmt
on the code base before submitting (on latest nightly with rustfmt support)Issues
Helps with #89, but doesn't really fix it. Should improve our ability to spot actual coverage deficits, however.
Breaking Changes
None; no code was touched.
Other Changes