staged-recipes: travis api error
Not sure what this is about, but it is blocking staged recipes:
Traceback (most recent call last):
File "/home/runner/miniconda/bin/conda-smithy", line 10, in <module>
sys.exit(main())
File "/home/runner/miniconda/lib/python3.7/site-packages/conda_smithy/cli.py", line 666, in main
args.subcommand_func(args)
File "/home/runner/miniconda/lib/python3.7/site-packages/conda_smithy/cli.py", line 291, in __call__
ci_register.travis_configure(owner, repo)
File "/home/runner/miniconda/lib/python3.7/site-packages/conda_smithy/ci_register.py", line 502, in travis_configure
response.raise_for_status()
File "/home/runner/miniconda/lib/python3.7/site-packages/requests/models.py", line 953, in raise_for_status
raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 403 Client Error: Forbidden for url: https://api.travis-ci.com/repo/20663660/setting/builds_only_with_travis_yml
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 2
- Comments: 19 (19 by maintainers)
Travis is investigating
I’ve opened an issue on the status page about it: https://github.com/conda-forge/status/issues/116
Travis syncing stuff is flaky. When a user has admin access to 5000+ repos and the repos are checked in a random order, it’s pure chance that travis finds out that the user has admin access to a repo before running out of API requests. That’s why we setup a way to have a bot-user that is not an org-wide admin, so that it doesn’t have admin access to 5000+ repos.
Why would that matter? This worked fine for the past few days. Travis changed something again.
Well we may need to turn Travis off then. We are using an admin on the repo to make the api calls. Further, nobody at Travis wrote me back after my support ticket. I’m not sure what else to do here.
Cc @conda-forge/core
This has been occurring all day today (15-Aug) for the [new] pyannote.metrics-feedstock. The action itself reports success despite the fact that the feedstock isn’t created and/or set up properly.