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

Delete this message

Reply to this message
Autor: tails-ci
Data:  
Dla: tails-l10n
Stare tematy: [Tails-l10n] Build failed in Jenkins: check_PO_master #5481
Nowe tematy: [Tails-l10n] Build failed in Jenkins: check_PO_master #5483
Temat: [Tails-l10n] Build failed in Jenkins: check_PO_master #5482
See <https://jenkins.tails.boum.org/job/check_PO_master/5482/display/redirect?page=changes>

Changes:

[sajolida] Fix broken link


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

Commit message: "Fix broken link"
> git rev-list --no-walk 50380b00e6fc1d0fa9ead5496c1b9661cf08af6b # timeout=10

[check_PO_master] $ /bin/sh -xe /tmp/jenkins6831395745482639185.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