Skip to content

fix paths for scrutinizer #32

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

Merged
merged 1 commit into from
Jan 15, 2016
Merged

fix paths for scrutinizer #32

merged 1 commit into from
Jan 15, 2016

Conversation

dbu
Copy link
Collaborator

@dbu dbu commented Jan 15, 2016

No description provided.

@dbu
Copy link
Collaborator Author

dbu commented Jan 15, 2016

@sagikazarmark any idea why scrutinizer fails here? even if some of the tests fail scrutinizer should still work i think.

@sagikazarmark
Copy link
Member

@dbu Travis fails and scrutinizer waits for external code coverage. Feel free to merge this, problem will be solved once tests are back to green.

@dbu
Copy link
Collaborator Author

dbu commented Jan 15, 2016 via email

@sagikazarmark
Copy link
Member

Coverage is uploaded by the travis script in the after_success hook. Otherwise coverage is not generated at all. If no coverage is received by scrutinizer in a given time (300 seconds by default I think) then it fails.

dbu added a commit that referenced this pull request Jan 15, 2016
@dbu dbu merged commit 62e1670 into master Jan 15, 2016
@dbu dbu deleted the scrutinizer branch January 15, 2016 11:51
@dbu
Copy link
Collaborator Author

dbu commented Jan 15, 2016

ah, makes sense. lets hope puli can be fixed soon

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.

2 participants