Where are the translation tests in the pipeline?

tessus · 30 November 2020 18:58

I remember the pipeline also built the translations so we could see, if there were any errors.

But I don't see that in the output anymore. Was this removed or did I miss it in the output?

laurent · 30 November 2020 19:57

It still there and should still run but maybe it doesn't output anything when the translation is valid. Or does it use to?

github.com

laurent22/joplin/blob/48e3811fbdbfd446a7fc2b33f34331bf0bb0c0f7/.travis.yml#L95


# Run linter for pull requests only - this is so that
# bypassing eslint is allowed for urgent fixes.
if [ "$TRAVIS_PULL_REQUEST" != "false" ]; then
  npm run linter-ci ./
  testResult=$?
  if [ $testResult -ne 0 ]; then
    exit $testResult
  fi
fi
# Validate translations - this is needed as some users manually
# edit .po files (and often make mistakes) instead of using a proper
# tool like poedit. Doing it for Linux only is sufficient.
if [ "$TRAVIS_PULL_REQUEST" != "false" ]; then
  if [ "$TRAVIS_OS_NAME" != "osx" ]; then
    node packages/tools/validate-translation.js
    testResult=$?
    if [ $testResult -ne 0 ]; then
      exit $testResult
    fi
  fi

tessus · 30 November 2020 20:37

I thought it would print a success message or something. Maybe I was wrong.

Topic		Replies	Views
Pull requests and commits failing on CI Development	5	502	13 March 2021
Travis is broken? Development	5	514	22 March 2020
Building translations no longer works Development	3	605	10 June 2020
Building Translation Development	4	798	29 May 2018
"npm test" failing GSoC	2	898	13 March 2021

Where are the translation tests in the pipeline?

Related Topics