Skip to content
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

[azure-pipelines | analyzer] Integrate Code Coverage #106

Closed
7 of 8 tasks
Raffaello opened this issue May 10, 2020 · 6 comments · Fixed by #110
Closed
7 of 8 tasks

[azure-pipelines | analyzer] Integrate Code Coverage #106

Raffaello opened this issue May 10, 2020 · 6 comments · Fixed by #110
Assignees
Labels
configuration cmake or project related code, configuaration
Milestone

Comments

@Raffaello
Copy link
Owner

Raffaello commented May 10, 2020

Scenario:
Linux CI images are probably headless and no video drivers, so impossible to init SDL2 for testing.
consequently:

  • compiling with GCC in Windows or Mac
  • MinGW (it might not worth it) [ error: unreference winMain]
  • GCC on macOS (this might be closer to linux, less compatibility problems) [problem linking the dependeny.. should i force to compile them in GCC? try]
  • use codecov
  • use sonarcloud

[Optional] Try other CI tools

  • travis
  • [ ] CircleCI
  • container CI build? [not yet supported windows host container linux]

  • clang code coverage
@Raffaello Raffaello added the configuration cmake or project related code, configuaration label May 10, 2020
@Raffaello Raffaello added this to the Better CI milestone May 10, 2020
@Raffaello Raffaello changed the title Integrate Code Coverage in CI [azure-pipelines | Analyzer Stage] Integrate Code Coverage in CI May 10, 2020
@Raffaello Raffaello changed the title [azure-pipelines | Analyzer Stage] Integrate Code Coverage in CI [azure-pipelines | Analyzer] Integrate Code Coverage in CI May 10, 2020
@Raffaello Raffaello changed the title [azure-pipelines | Analyzer] Integrate Code Coverage in CI [azure-pipelines | Analyzer] Integrate Code Coverage May 10, 2020
@Raffaello Raffaello changed the title [azure-pipelines | Analyzer] Integrate Code Coverage [azure-pipelines | analyzer] Integrate Code Coverage May 10, 2020
@Raffaello
Copy link
Owner Author

this is the snippet (BASH/UNIX-Debian) to generate and publish results in codecov

sudo apt-get install -y lcov 
#find . -name *gcda
lcov --capture --directory . --output-file coverage.info
lcov --remove coverage.info '/usr/*' --output-file coverage.info # filter system-files
lcov --list coverage.info # debug info
bash <(curl -s https://codecov.io/bash) -t [codecov token]

@Raffaello Raffaello linked a pull request May 10, 2020 that will close this issue
4 tasks
@Raffaello
Copy link
Owner Author

Raffaello commented May 10, 2020

too many linking problem just to compile it and not a way to have on local env at the moment.
should try once a container test for linux to run on a windows or mac vm, if that is possible than should be ok

ref:
https://docs.microsoft.com/en-us/azure/devops/pipelines/process/container-phases?view=azure-devops

Run pipeline jobs inside of a container

@Raffaello
Copy link
Owner Author

Raffaello commented May 10, 2020

@Raffaello
Copy link
Owner Author

Raffaello commented May 11, 2020

this is the snippet (BASH/UNIX-Debian) to generate and publish results in codecov

sudo apt-get install -y lcov 
#find . -name *gcda
lcov --capture --directory . --output-file coverage.info
lcov --remove coverage.info '/usr/*' --output-file coverage.info # filter system-files
lcov --list coverage.info # debug info
bash <(curl -s https://codecov.io/bash) -f coverage.info -t [codecov token]

for clang:
codecov/codecov-python#52 (comment)

@Raffaello Raffaello self-assigned this May 11, 2020
@Raffaello
Copy link
Owner Author

Raffaello commented May 11, 2020

@Raffaello
Copy link
Owner Author

Raffaello commented May 11, 2020

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
configuration cmake or project related code, configuaration
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant