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

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 #5479
Nuovi argomenti: [Tails-l10n] Build failed in Jenkins: check_PO_master #5481
Oggetto: [Tails-l10n] Build failed in Jenkins: check_PO_master #5480
See <https://jenkins.tails.boum.org/job/check_PO_master/5480/display/redirect>

Changes:


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

Commit message: "merge with main git using update_weblate_git.py."
> git rev-list --no-walk 1d505dae46e8a0ff44aff6504da8c6c583fd7953 # timeout=10

[check_PO_master] $ /bin/sh -xe /tmp/jenkins8221051261682290676.sh
+ /var/lib/jenkins/tools/slaves/check_po
ERROR: wiki/src/news/plans_for_2020.fr.po:
    i18nspector is not happy:
        E: inconsistent-trailing-newlines msgid 'Currently, many have to learn how to disable Secure Boot on their\ncomputer. This process is slightly different on every computer, is very\ncomplicated to learn on your own, and can lead to scary problems on\nWindows computers, for example [[!tails_ticket 15016#note-19\ndesc="*BitLocker* asking you for a recovery key"]].\n'
checked files are not clean.
Build step 'Execute shell' marked build as failure