-
Notifications
You must be signed in to change notification settings - Fork 284
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
Apidsl fixes and start tracking test coverage #1
Conversation
Changes Unknown when pulling 71860a3 on iphydf:master into * on TokTok:master*. |
acff665
to
071b4b3
Compare
Changes Unknown when pulling 071b4b3 on iphydf:master into * on TokTok:master*. |
Changes Unknown when pulling 071b4b3 on iphydf:master into * on TokTok:master*. |
@iphydf any reason why @DeriveFH (irungentoo#1542) is not attributed for |
Review status: 0 of 3 files reviewed at latest revision, 4 unresolved discussions. .travis.yml, line 2 [r1] (raw file):
Why are we switching Travis away from using Ubuntu 14.04 to Ubuntu 12.04? https://docs.travis-ci.com/user/ci-environment/#Virtualization-environments Ubuntu 14.04 has libconfig-dev, libvpx-dev, libopus-dev and check in it's package repos, which eliminates all the building you do below in this file. .travis.yml, line 17 [r1] (raw file):
Hm, you want to cache all the builds to save time it takes for Travis to run? It looks okay. .travis.yml, line 73 [r1] (raw file):
Most of this building is not necessary if Ubuntu 14.04 is used. .travis.yml, line 90 [r1] (raw file):
Doesn't Travis already fail a build if any of commands exit with non 0 code? Comments from Reviewable |
Review status: 0 of 3 files reviewed at latest revision, 4 unresolved discussions. .travis.yml, line 90 [r1] (raw file):
|
I didn't know that PR existed when I made my changes, but I'm happy to incorporate commits from there. I'll back out my changes. Review status: 0 of 3 files reviewed at latest revision, 4 unresolved discussions. .travis.yml, line 2 [r1] (raw file):
|
Review status: 0 of 3 files reviewed at latest revision, 1 unresolved discussion. .travis.yml, line 73 [r1] (raw file):
|
- We use coveralls.io to report on test coverage and avoid getting below a certain threshold. The threshold is currently 60%, but we will be increasing it when it stabilises. - We use gcc/clang -ftest-coverage and gcov to measure C test coverage. - We switched to container based Travis build infrastructure, which has the advantage of faster boot times[1] (1-6s vs. 20-52s). The trusty beta supports caching, but the longer boot times make it an unattractive target. - We now need to build more dependencies ourselves and cache the result. We still fetch what we can (currently opam, libvpx, and check) from apt. [1] https://docs.travis-ci.com/user/ci-environment/#Virtualization-environments
@yashikno I've merged your changes here. Thanks for making them. |
Changes Unknown when pulling 83f5258 on iphydf:master into * on TokTok:master*. |
Review status: 0 of 3 files reviewed at latest revision, 1 unresolved discussion. .travis.yml, line 73 [r1] (raw file):
|
How/where is the 60% of code coverage enforced? |
Unfortunately, that is currently only set on the coveralls settings page. I hope to get codecov.io submission working at some point, and then the setting is in a codecov.yml file. |
Reviewed 1 of 3 files at r1, 2 of 2 files at r3. Comments from Reviewable |
Hm, reviewable shows me a "Merge & Retain Branch", which is interesting as I shouldn't have permissions to push into this repo. |
This change is