[Tails-l10n] Build failed in Jenkins: check_PO_master #5309

このメッセージを削除

このメッセージに返信
著者: tails-ci
日付:  
To: tails-l10n
古いトピック: [Tails-l10n] Build failed in Jenkins: check_PO_master #5308
新しいトピック: [Tails-l10n] Build failed in Jenkins: check_PO_master #5310
題目: [Tails-l10n] Build failed in Jenkins: check_PO_master #5309
See <https://jenkins.tails.boum.org/job/check_PO_master/5309/display/redirect?page=changes>

Changes:

[intrigeri] Revert spam


------------------------------------------
Started by an SCM change
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on isobuilder3 in workspace <https://jenkins.tails.boum.org/job/check_PO_master/ws/>
No credentials specified
Wiping out workspace first.
Cloning the remote Git repository
Cloning repository gitolite3@???:tails
> git init <https://jenkins.tails.boum.org/job/check_PO_master/ws/> # timeout=10

Fetching upstream changes from gitolite3@???:tails
> git --version # timeout=10
> git fetch --tags --progress -- gitolite3@???:tails +refs/heads/*:refs/remotes/origin/*
> git config remote.origin.url gitolite3@???:tails # timeout=10
> git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
> git config remote.origin.url gitolite3@???:tails # timeout=10

Fetching upstream changes from gitolite3@???:tails
> git fetch --tags --progress -- gitolite3@???:tails +refs/heads/*:refs/remotes/origin/*
> git rev-parse origin/master^{commit} # timeout=10

Checking out Revision 0e94339501114fb2518bc4de85ee283a54e289b8 (origin/master)
> git config core.sparsecheckout # timeout=10
> git checkout -f 0e94339501114fb2518bc4de85ee283a54e289b8

Commit message: "Revert spam"
> git rev-list --no-walk ed8a310b200af865e2b07e8e5ef39f6e829c2ea0 # timeout=10

[check_PO_master] $ /bin/sh -xe /tmp/jenkins8549235537118753432.sh
+ /var/lib/jenkins/tools/slaves/check_po
ERROR: wiki/src/about/contact.pt.po:
    i18nspector is not happy:
        E: inconsistent-trailing-newlines msgid '[[!toc levels=2]]\n'
checked files are not clean.
Build step 'Execute shell' marked build as failure