Opened 4 years ago

Closed 4 years ago

#1338 closed defect/bug (fixed)

CircleCI fails on translation update when running on trunk of forked repo

Reported by: mvglasow (2) Owned by: KaZeR
Priority: major Milestone:
Component: core Version: git master
Severity: normal Keywords: ci, toolchain
Cc:

Description

I see CircleCI tests frequently failing when updating translations. The command is the following:

curl "https://translations.launchpad.net/navit/${CIRCLE_BRANCH}/+translations-upload" -H "$lp_cookie" -H "Referer: https://translations.launchpad.net/navit/${CIRCLE_BRANCH}/+translations-upload" -F file=@bin/po/navit.pot | grep title

Exit code is 1 and output is the following:

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed


curl "https://translations.launchpad.net/navit/${CIRCLE_BRANCH}/+translations-upload" -H "$lp_cookie" -H "Referer: https://translations.launchpad.net/navit/${CIRCLE_BRANCH}/+translations-upload" -F file=@bin/po/navit.pot | grep title returned exit code 1

100 37058 100 86 100 36972 164 70742 --:--:-- --:--:-- --:--:-- 83270 Action failed: curl "https://translations.launchpad.net/navit/${CIRCLE_BRANCH}/+translations-upload" -H "$lp_cookie" -H "Referer: https://translations.launchpad.net/navit/${CIRCLE_BRANCH}/+translations-upload" -F file=@bin/po/navit.pot | grep title

I've only seen it happen on my own repo and on the trunk branch, not on the official (navit-gps) repo nor on any other branch. This makes it impossible to verify on something I've committed to my own trunk before pushing it to the main repo.

I'm no expert on this, but I believe I shouldn't be uploading any translations from a private fork of Navit. Thus, this step should probably include a check to determine whether Navit was cloned from the main repo, and if not, this step should be skipped.

Change History (4)

comment:1 Changed 4 years ago by tryagain

Please test if this commit would fix your problem...

comment:2 Changed 4 years ago by mvglasow (2)

This seems to have fixed the curl error but another one has popped up during deployment:

https://circleci.com/gh/mvglasow/navit/28

git push origin $CIRCLE_SHA1:refs/heads/master fails with exit code 128, output is:

ERROR: The key you are authenticating with has been marked as read only.
fatal: Could not read from remote repository.

Please make sure you have the correct access rights

git push origin $CIRCLE_SHA1:refs/heads/master returned exit code 128

and the repository exists. Action failed: git push origin $CIRCLE_SHA1:refs/heads/master

comment:3 Changed 4 years ago by kazer

Please test if this commit would fix this problem.

comment:4 Changed 4 years ago by mvglasow (2)

  • Resolution set to fixed
  • Status changed from new to closed

Thanks, this solved it for good! I'll close this issue.

Note: See TracTickets for help on using tickets.