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

このメッセージを削除

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

Changes:

[tails-l10n] Weblate commit


------------------------------------------
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 7606a032c25f3961c2c49f86be0c4258404af290 (origin/master)
> git config core.sparsecheckout # timeout=10
> git checkout -f 7606a032c25f3961c2c49f86be0c4258404af290

Commit message: "Weblate commit"
> git rev-list --no-walk 0f5d0b26ea88f4d54a058e40fa55bb37dc688c95 # timeout=10

[check_PO_master] $ /bin/sh -xe /tmp/jenkins1330296783659788291.sh
+ /var/lib/jenkins/tools/slaves/check_po
ERROR: wiki/src/doc/first_steps/persistence.pt.po:
    i18nspector is not happy:
        E: inconsistent-trailing-newlines msgid 'If you start Tails from a USB stick, you can create a persistent volume in the free space left on the USB stick.  The files in the persistent volume are saved encrypted and remain available across separate working sessions.'
checked files are not clean.
Build step 'Execute shell' marked build as failure