-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
crowdin error when trying to execute tests locally #3977
Comments
A workaround that I do for testing is to remove that section from Note: make sure not to commit these changes. |
In that case, I believe a script like run-tests.sh that modifies the file appropriately would be needed. If that's too hard or impossible for some other reason, a mention in the readme would suffice. |
Maybe a new ENV local could be added so that ignore some tests. |
@devil418 You can get an API key for crowdin by signing up at their site, then looking under your account settings. I haven't figured out where to put it yet though... (later edit:) (still later:) Okay, I'm going to conclude that [docker_docs:L341:124s] + /usr/local/bin/docker tag 00000000 gitea/docs:latest [docker_docs:L342:124s] + /usr/local/bin/docker push gitea/docs:latest [docker_docs:L343:124s] The push refers to a repository [docker.io/gitea/docs] [docker_docs:L344:125s] dcb9aa504a9c: Preparing [docker_docs:L345:125s] 97d75450208b: Preparing [docker_docs:L346:125s] 00ce309518aa: Preparing [docker_docs:L347:125s] f295bdb1762a: Preparing [docker_docs:L348:125s] c9e8b5c053a2: Preparing [docker_docs:L349:125s] denied: requested access to the resource is denied [docker_docs:L350:125s] time="2018-05-26T21:13:44Z" level=fatal msg="exit status 1" |
[x]
):drone exec
https://pastebin.com/DFhL8L43Description
WHen executing 'drone exec' in the gitea directory, the tests fail. I get a long log (link above), but those two lines seem to be the most important:
It seems that to execute tests, I need an api key for crowdin? Is that true, and, if so, how to optain it?
The text was updated successfully, but these errors were encountered: