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

Delete this message

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

Changes:

[intrigeri] Unfuzzy translations.

------------------------------------------
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 2c90da32ddbec9503a000bf790a1a06db4affdc0 (origin/master)
> git config core.sparsecheckout # timeout=10
> git checkout -f 2c90da32ddbec9503a000bf790a1a06db4affdc0
> git rev-list 14de6f14151d62b4ab5c40a8d12848a7d854d663 # timeout=10

[check_PO_master] $ /bin/sh -xe /tmp/hudson1362828048082482100.sh
+ /var/lib/jenkins/tools/slaves/check_po
E: ./wiki/src/upgrade.de.po: syntax-error-in-po-file line 75
E: ./wiki/src/upgrade.fr.po: syntax-error-in-po-file line 75
E: ./wiki/src/upgrade.pt.po: syntax-error-in-po-file line 75Build step 'Execute shell' marked build as failure