-
-
Notifications
You must be signed in to change notification settings - Fork 4
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
Update Travis tests for Ubuntu Precise. #135
Comments
Copying from npr/nprapi-wordpress#46: Based on research in npr/pmp-php-sdk#36,
Reasons that given versions of WordPress have tests incompatible with travis-ci.org:
During conversation today, we decided to target the last pre-Gutenberg WordPress version and the most-recent 2 releases: 4.9, 5.0, 5.1. For PHP versions, I think we should take the same approach: current supported and last pre-7 PHP version. |
PHPunit 8 requires PHP > 7.2, and the WordPress trac ticket for PHPunit 8 support is this one. The list of currently-supported PHPunit/PHP combinations can be found at https://phpunit.de/supported-versions.html The list of currently-supported PHP versions can be found at https://secure.php.net/supported-versions.php |
A review of tests initially introduced in #138: https://travis-ci.org/INN/link-roundups/builds/502881348?utm_source=github_status&utm_medium=notification
|
… due to a lack of backports: #135 (comment)
…sts are not supported by WordPress at this time. See research described in #135 (comment) A review of tests initially introduced in #138: https://travis-ci.org/INN/link-roundups/builds/502881348?utm_source=github_status&utm_medium=notification - Travis is running PHP 7.2 with PHPunit 8. https://travis-ci.org/INN/link-roundups/jobs/502881355 - Travis is running PHP 7.3 with PHPunit 8. https://travis-ci.org/INN/link-roundups/jobs/502881358 - WP 4.9/5.0 don't have PHPUnit 8 forwards-compatibility shims in place; 5.1 does provide a warning about 8 not being supported.
Basically, copy the work from npr/nprapi-wordpress#46 and put it in this plugin's
.travis.yml
, and make sure that the tests run. They don't have to run successfully for this issue to be marked complete, but they do need to run.The text was updated successfully, but these errors were encountered: