vokal / cvr Goto Github PK

View Code? Open in Web Editor NEW

8.0 16.0 5.0 116 KB

Code Coverage

License: MIT License

Shell 0.62% HTML 0.74% CSS 10.39% JavaScript 88.26%

cvr's People

Contributors

Stargazers

Watchers

Forkers

jrit foresmac qingguo-yu workhorseindustries

cvr's Issues

Register a user and associated repos

Build a good frontend to browse coverage info

Parse Java coverage (cobertura)

Jacoco (Android) Coverage

I wanted to open a ticket to support jacoco coverage with vokal/jacoco-parse

There are a few issues with Android source structure that might be a problem with finding the appropriate files for linking.

For example:

An android application with a Mock and Live "Flavor" will have the source structured like so:

... //Root project files
app/
    src/
        mock/java/
        main/java/
        live/java/

Additionally we will mostly likely need to specify the root folder for the project as the source is located in any arbitrary subfolder of the main project. In the example above that folder is app

Currently reporting is via a fairly ugly curl command which could be considerably cleaner. Ignoring the implementation details, which make sense in my head but I haven't put together yet, this is what I would propose:

Reduce:
curl --data "token=$CVR_TOKEN&commit=$GITHASH&coverage=$COVERAGE&coveragetype=cobertura" https://cvr.vokal.io/coverage

Down to:

curl -sSL https://cvr.vokal.io/coverage/$$cvrToken | sh

I'll tackle implementing this. Like I said I have thoughts. So ignoring the question of how I infer all of the additional data, any concerns over this approach?

Parse Python coverage (cobertura)

Parse iOS Coverage, whatever that is

Add ability to convert from one coverage format to another

It would be awesome if I could convert from any of the formats support for parsing to another format. i.e JaCoCo -> LCOV, Go Cover -> Clover, etc.

Python files marked as "clike"

I presume this is use for syntax highlighting? Probably pretty safe to just assume any file that ends in .py is a Python file.

De-register github hook when deleting a repo

Can't parse go coverage reports?

Not sure, this uploaded to cvr but it's not listing. Maybe I need the prepend path?

mode: count
vip/handler.go:44.31,47.2 2 0
vip/handler.go:49.71,54.16 4 7
vip/handler.go:59.2,61.34 2 7
vip/handler.go:73.2,74.23 2 7
vip/handler.go:78.2,78.21 1 7
vip/handler.go:83.2,83.35 1 6
vip/handler.go:87.2,87.9 1 5
vip/handler.go:54.16,57.3 2 0
vip/handler.go:61.34,63.12 2 10
vip/handler.go:63.12,69.9 5 3
vip/handler.go:74.23,76.3 1 3
vip/handler.go:78.21,81.3 2 1
vip/handler.go:83.35,85.3 1 1
vip/handler.go:90.59,97.2 5 6
vip/handler.go:99.58,101.12 2 1
vip/handler.go:106.2,106.75 1 1
vip/handler.go:101.12,103.3 1 0
vip/handler.go:103.3,105.3 1 1
vip/handler.go:109.59,112.45 2 0
vip/handler.go:116.2,116.30 1 0
vip/handler.go:112.45,115.3 2 0
vip/handler.go:119.65,120.23 1 0
vip/handler.go:124.2,128.45 2 0
vip/handler.go:133.2,137.16 4 0
vip/handler.go:141.2,142.119 2 0
vip/handler.go:120.23,122.3 1 0
vip/handler.go:128.45,131.3 2 0
vip/handler.go:137.16,139.3 1 0
vip/handler.go:145.59,146.24 1 5
vip/handler.go:151.2,151.33 1 5
vip/handler.go:167.2,172.16 5 4
vip/handler.go:176.2,180.16 3 4
vip/handler.go:185.2,187.22 2 4
vip/handler.go:196.2,205.45 5 4
vip/handler.go:146.24,149.3 2 0
vip/handler.go:151.33,158.3 4 0
vip/handler.go:158.3,158.33 1 5
vip/handler.go:158.33,165.3 4 1
vip/handler.go:172.16,174.3 1 0
vip/handler.go:180.16,183.3 2 0
vip/handler.go:187.22,189.13 2 0
vip/handler.go:189.13,191.4 1 0
vip/handler.go:191.4,193.4 1 0
vip/handler.go:205.45,208.3 2 1
vip/handler.go:211.57,214.2 2 0
vip/handler.go:216.82,217.49 1 6
vip/handler.go:217.49,219.17 2 5
vip/handler.go:222.3,222.23 1 5
vip/handler.go:226.3,232.17 6 5
vip/handler.go:235.3,237.45 2 5
vip/handler.go:219.17,221.4 1 0
vip/handler.go:222.23,224.4 1 0
vip/handler.go:232.17,234.4 1 0
vip/handler.go:239.3,241.17 2 1
vip/handler.go:245.3,248.17 4 1
vip/handler.go:252.3,258.45 5 1
vip/handler.go:241.17,243.4 1 0
vip/handler.go:248.17,250.4 1 0
vip/main.go:44.19,49.12 3 0
vip/main.go:49.12,53.39 3 0
vip/main.go:57.3,57.77 1 0
vip/main.go:53.39,55.4 1 0
vip/main.go:57.77,59.4 1 0
vip/main.go:60.3,61.56 1 0
vip/main.go:61.56,63.4 1 0
vip/main.go:67.29,70.8 3 2
vip/main.go:70.8,72.3 1 1
vip/main.go:72.3,77.3 2 1
vip/main.go:80.13,86.16 6 1
vip/main.go:91.2,92.16 2 1
vip/main.go:97.2,101.21 4 1
vip/main.go:105.2,106.25 2 1
vip/main.go:113.2,114.24 2 1
vip/main.go:122.2,132.21 9 1
vip/main.go:86.16,89.3 2 1
vip/main.go:92.16,95.3 2 1
vip/main.go:101.21,103.3 1 1
vip/main.go:106.25,108.3 1 1
vip/main.go:108.3,111.3 2 0
vip/main.go:114.24,116.3 1 1
vip/main.go:116.3,118.17 2 0
vip/main.go:118.17,120.4 1 0
vip/main.go:135.13,139.16 3 0
vip/main.go:143.2,148.60 4 0
vip/main.go:152.2,153.70 1 0
vip/main.go:164.2,164.15 1 0
vip/main.go:174.2,182.20 6 0
vip/main.go:139.16,141.3 1 0
vip/main.go:148.60,150.3 1 0
vip/main.go:153.70,157.18 3 0
vip/main.go:161.4,161.27 1 0
vip/main.go:157.18,159.5 1 0
vip/main.go:164.15,166.17 2 0
vip/main.go:166.17,169.4 2 0
vip/main.go:169.4,171.4 1 0

Parse Go coverage

Data too large, sort failure

When uploading an apparently-large cobertura.xml, we're getting this error:

Executor error: Overflow sort stage buffered data usage of 34777516 bytes exceeds internal limit of 33554432 bytes

Example: https://travis-ci.com/vokal/Brandish-iOS/builds/21463613#L4117

504 timeout errors on cvr.vokal.io

I'm seeing 504 errors today when trying to upload code coverage from Travis (LCOV):
https://magnum.travis-ci.com/vokal/ThousandTrails-iOS/builds/16732660#L2716-L2721

The upload was working on Friday (10/16) with the same script:
https://github.com/vokal/ThousandTrails-iOS/blob/master/travis/codecov.sh#L12-L13

I'm also seeing a 504 error here: https://cvr.vokal.io/repos

Express Setup

Add github hooks

It would be nice if this would post the results of a coverage check to github showing the percentage of code covered and a link to view details. And, do we want a configurable threshold for successful build, or standardize on 95%?

The benefit here is that a code reviewer can know how much code is covered at a glance while a project dev can always click over to view details if something is off.