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

adding badges #5

Merged
merged 5 commits into from May 18, 2017
Merged

adding badges #5

merged 5 commits into from May 18, 2017

Conversation

brozeph
Copy link
Contributor

@brozeph brozeph commented May 12, 2017

We'll need to get coverage up - I haven't looked closely, but perhaps it's a weird issue with how coveralls interprets the reports.

Additionally, note the missing dependencies that were required to get the build to work properly. These little details are killers (https://travis-ci.org/PlayNetwork/fs-promise-util/jobs/231622328#L420).

@coveralls
Copy link

Coverage Status

Changes Unknown when pulling 9d1c658 on v1.0.1 into ** on master**.

1 similar comment
@coveralls
Copy link

Coverage Status

Changes Unknown when pulling 9d1c658 on v1.0.1 into ** on master**.

@coveralls
Copy link

coveralls commented May 12, 2017

Coverage Status

Changes Unknown when pulling 4901076 on v1.0.1 into ** on master**.

@coveralls
Copy link

coveralls commented May 12, 2017

Coverage Status

Changes Unknown when pulling 29f3ac9 on v1.0.1 into ** on master**.

@sanakanchha
Copy link
Contributor

@brozeph yeah, looks like the report interpretation is different with coveralls since the coverage is above 80% while running the tests.

@sanakanchha
Copy link
Contributor

Also, the build is failing as it is pointing to master and there is no code to build in master.
Build Status

Just to test, I changed the branch to v1.0.1 and that passes the build.
[Build Status]

Hence, once v1.0.1 is merged to master, build passes.

@sanakanchha
Copy link
Contributor

Looking into why the coveralls reports less % code coverage. Also will look into bumping up the coverage.

@sanakanchha
Copy link
Contributor

sanakanchha commented May 13, 2017

@brozeph added test that bumped code coverage above 90%
Build StatusCoverage Status

@coveralls
Copy link

coveralls commented May 13, 2017

Coverage Status

Changes Unknown when pulling 20bbfd9 on v1.0.1 into ** on master**.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants