-
Notifications
You must be signed in to change notification settings - Fork 118
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
Fix travis #804
Fix travis #804
Conversation
- $SCRIPT_DIR/run-tests.sh "islandora_text_extraction" | ||
|
||
after_success: | ||
- bash <(curl -s https://codecov.io/bash) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you add this line back in at the end of after_success
will we get codecov back? I'm trying to think about how it would all play out in this scenario. Is it possible to still have codecov with this approach?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We don't use codecov for Drupal modules do we?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can have codecov, I disabled xdebug to get the speed increase and because we didn't seem to ever use codecov for Drupal modules. It can be re-enabled if you desire.
no need thanks to #805 |
Travis is broken.
This PR includes:
What does this Pull Request do?
Breaks out the tests into three different categories.
Also includes/tests two other travis fixes.
What's new?
Automated testing is now separating out kernel, functional, and functional javascript.
How should this be tested?
Does Travis pass?
Additional Notes:
Interested parties
Tag @whikloj @dannylamb @Islandora/7-x-1-x-committers