Since switching plugins.svn.wordpress.org linting to PHP7 it looks like the fatal error outputs are not including the actual error, only the fact an error occured. This causes a bit of confusion as some things are being blocked (correctly) with no obvious cause.
For example:
Sending plugin.php Transmitting file data .svn: E165001: Commit failed (details follow): svn: E165001: Commit blocked by pre-commit hook (exit code 1) with output: *********************************** PHP error in: test-plugin-3/trunk/plugin.php: Errors parsing test-plugin-3/trunk/plugin.php *********************************** svn: E165001: Your commit message was left in a temporary file: svn: E165001: '/home/www/tmp/sdf/svn-commit.tmp'
In that case, it should’ve included a message of Fatal error: 'continue' not in the 'loop' or 'switch' context in plugin.php on line 20
(Note: This is one of the new PHP7 parse fatal errors)
This can be tested by attempting to commit to a pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party with a continue;
statement in global scope (for example, a file as <?php continue;
).
I can’t see the issue in the pre-commit script, but i assume the error is probably going to STDOUT rather than STDERR.