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

Delete this message

Reply to this message
Author: tails-ci
Date:  
To: tails-l10n
New-Topics: [Tails-l10n] Build failed in Jenkins: check_PO_master #4385
Subject: [Tails-l10n] Build failed in Jenkins: check_PO_master #4384
See <https://jenkins.tails.boum.org/job/check_PO_master/4384/changes>

Changes:

[tails-l10n] Translated using Weblate (Spanish)

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

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

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

Checking out Revision 48f91a5434a98c522ac50f7f9bd7a8201f46928c (origin/master)
> git config core.sparsecheckout # timeout=10
> git checkout -f 48f91a5434a98c522ac50f7f9bd7a8201f46928c
> git rev-list 2770333b35f2d34b2090674171301f0ce1e99703 # timeout=10

[check_PO_master] $ /bin/sh -xe /tmp/hudson3289075873749332019.sh
+ /var/lib/jenkins/tools/slaves/check_po
ERROR: wiki/src/install/inc/steps/clone.inline.es.po:
    i18nspector is not happy:
        E: inconsistent-trailing-newlines msgid '   <div class="caution install-clone mac-clone">\n   <p>All the data on this USB stick will be lost.</p>\n   </div>\n'
checked files are not clean.
Build step 'Execute shell' marked build as failure