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

Delete this message

Reply to this message
Autore: tails-ci
Data:  
To: tails-l10n
Vecchi argomenti: [Tails-l10n] Build failed in Jenkins: check_PO_master #4677
Nuovi argomenti: [Tails-l10n] Build failed in Jenkins: check_PO_master #4679
Oggetto: [Tails-l10n] Build failed in Jenkins: check_PO_master #4678
See <https://jenkins.tails.boum.org/job/check_PO_master/4678/changes>

Changes:

[sajolida] Link to USB image first

------------------------------------------
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on isobuilder3 in workspace <https://jenkins.tails.boum.org/job/check_PO_master/ws/>
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 -c core.askpass=true fetch --tags --progress gitolite3@???:tails +refs/heads/*:refs/remotes/origin/*
> git config remote.origin.url gitolite3@???:tails # timeout=10
> git config 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 -c core.askpass=true fetch --tags --progress gitolite3@???:tails +refs/heads/*:refs/remotes/origin/*
> git rev-parse origin/master^{commit} # timeout=10

Checking out Revision 620519d6b73f784530eb089513dec34745fb23e9 (origin/master)
> git config core.sparsecheckout # timeout=10
> git checkout -f 620519d6b73f784530eb089513dec34745fb23e9
> git rev-list 03f087f37258222506d727f9151a86e47daaf331 # timeout=10

[check_PO_master] $ /bin/sh -xe /tmp/hudson844507913415880582.sh
+ /var/lib/jenkins/tools/slaves/check_po
ERROR: wiki/src/doc/first_steps/introduction_to_gnome_and_the_tails_desktop.es.po:
    i18nspector is not happy:
        E: inconsistent-trailing-newlines msgid 'System settings'
checked files are not clean.
Build step 'Execute shell' marked build as failure