Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Problem/Motivation
Sorry if this is a duplicate; it is currently impossible to search Drupal project issues for 'run-tests.sh'. Try it and see.
Follow-up to #2189345: run-tests.sh should exit with a failure code if any tests failed
run-tests.sh has incorrect docblocks and poor coding standards.
Let's fix that.
Proposed resolution
Fix it.
Remaining tasks
User interface changes
API changes
Data model changes
Comment | File | Size | Author |
---|---|---|---|
#13 | 2605290_12.patch | 16.22 KB | sanduhrs |
Comments
Comment #2
Mile23Comment #3
Mile23Comment #4
Mile23This patch changes all docblock coding standards errors, fixes some documentation errors, and makes very minor coding standards changes to executable code.
Comment #5
sanduhrsReroll and expansion.
no logic changes, just formatting.
Comment #7
sanduhrsAh, sorry this is based on #2189345: run-tests.sh should exit with a failure code if any tests failed, so the bot can't test it right now.
Comment #8
sanduhrs#2189345: run-tests.sh should exit with a failure code if any tests failed has been commited, this patch passes now.
Please review.
Comment #10
sanduhrsHide old patch.
Comment #11
Mile23+1.
Setting to RTBC even though it was my patch originally.
Comment #12
alexpottThe comma is not required at all. See https://3v4l.org/oIa3D
A can be on the previous line
Comment #13
sanduhrsYou are right of course – attached.
Comment #14
Mile23phpcs says the only remaining problems are global names, type hinting, and 'Use function ip_address() instead of $_SERVER['REMOTE_ADDR'].'
We can't fix those without changing code.
Marking RTBC again.
Comment #15
Mile23See also: #2624926: Refactor run-tests.sh for Console component.
Comment #16
alexpottCommitted b13967f and pushed to 8.0.x and 8.1.x. Thanks!