See <https://ci.phpmyadmin.net/job/phpMyAdmin-4.6/53/changes>
Changes:
[weblate] Translated using Weblate (Portuguese (Brazil))
------------------------------------------
Started by GitHub push by weblate
Started by GitHub push by weblate
[EnvInject] - Loading node environment variables.
Building in workspace <https://ci.phpmyadmin.net/job/phpMyAdmin-4.6/ws/>
> git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url git://github.com/phpmyadmin/phpmyadmin.git # timeout=10
Fetching upstream changes from git://github.com/phpmyadmin/phpmyadmin.git
> git --version # timeout=10
> git -c core.askpass=true fetch --tags --progress git://github.com/phpmyadmin/phpmyadmin.git +refs/heads/*:refs/remotes/origin/*
> git rev-parse origin/QA_4_6^{commit} # timeout=10
Checking out Revision 65052df07f49218a1edb38dbb61979fe70e934bc (origin/QA_4_6)
> git config core.sparsecheckout # timeout=10
> git checkout -f 65052df07f49218a1edb38dbb61979fe70e934bc
> git rev-list fdec3afe1b4ce4c41fa565ab819209ed5a0391c3 # timeout=10
[workspace] $ /bin/sh -xe /tmp/hudson7587340740772234138.sh
+ composer update --no-interaction
Warning: This development build of composer is over 60 days old. It is recommended to update it by running "/var/lib/jenkins/bin/composer self-update" to get the latest version.
Loading composer repositories with package information
Updating dependencies (including require-dev)
Nothing to install or update
Generating autoload files
+ ./scripts/generate-mo --quiet
po/pt_BR.po:4745: 'msgstr' is not a valid PHP format string, unlike 'msgid'. Reason: The string ends in the middle of a directive.
msgfmt: found 1 fatal error
tput: No value for $TERM and no -T specified
Error when compiling po/pt_BR.po
tput: No value for $TERM and no -T specified
Build step 'Execute shell' marked build as failure
[CHECKSTYLE] Skipping publisher since build result is FAILURE
[JSLINT] Skipping publisher since build result is FAILURE
[PMD] Skipping publisher since build result is FAILURE
[DRY] Collecting duplicate code analysis files...
[DRY] Finding all files that match the pattern build/logs/pmd-cpd.xml
[DRY] Parsing 1 file in <https://ci.phpmyadmin.net/job/phpMyAdmin-4.6/ws/>
[DRY] Successfully parsed file <https://ci.phpmyadmin.net/job/phpMyAdmin-4.6/ws/build/logs/pmd-cpd.xml> with 16 unique warnings and 0 duplicates.
[DRY] Computing warning deltas based on reference build #52
[TASKS] Skipping publisher since build result is FAILURE
[ANALYSIS-COLLECTOR] Computing warning deltas based on reference build #52
Recording plot data
Publishing Clover coverage report...
Clover xml file does not exist in: <https://ci.phpmyadmin.net/job/phpMyAdmin-4.6/ws/> called: build/logs/clover.xml and will not be copied to: /var/lib/jenkins/jobs/phpMyAdmin-4.6/builds/53/cloverphp/clover.xml
Could not find 'build/coverage/build/logs/clover.xml'. Did you generate the XML report for Clover?
[xUnit] [INFO] - Starting to record.
[xUnit] [INFO] - Processing PHPUnit-3.x (default)
[xUnit] [INFO] - [PHPUnit-3.x (default)] - 1 test report file(s) were found with the pattern 'build/logs/junit.xml' relative to '<https://ci.phpmyadmin.net/job/phpMyAdmin-4.6/ws/'> for the testing framework 'PHPUnit-3.x (default)'.
[xUnit] [ERROR] - Test reports were found but not all of them are new. Did all the tests run?
* <https://ci.phpmyadmin.net/job/phpMyAdmin-4.6/ws/build/logs/junit.xml> is 41 min old
[xUnit] [INFO] - Failing BUILD.
[xUnit] [INFO] - There are errors when processing test results.
[xUnit] [INFO] - Skipping tests recording.
[xUnit] [INFO] - Stop build.
[JDepend] JDepend plugin is ready
[JDepend] Found 2827 classes in 301 packages
For those of you who are subscribed to the GitHub notification email messages, I certainly feel bad about all the spam that you're receiving. Unfortunately, it's not something that GitHub gives repository owners the power to control; it's been reported to the GitHub administrators who will eventually block the user universally.
As a reminder, you're able to block that user from sending notifications to you personally; go to one of the comments and click his username to go to the accounts page. Kind of in the upper right region, there's a small dropbox which has options to both block the user and report them to GitHub (which you may wish to do).