All Systems Mostly Operational

Repos and Bots

admin web services status: No Status Available
libcfgraph status:
CDN cloning status: operational

Current Migrations

Long-running Migrations
Other Migrations
Recently Closed Migrations
Nothing here! Yay!

Version Updates

Azure Pipelines Usage

Azure Pipelines usage is not available.

GitHub Actions Usage

GitHub Actions usage is not available.

Travis CI Usage

Travis CI usage is not available.

Drone Usage

Drone usage is not available.

CircleCI Usage

CircleCI usage is not available.

AppVeyor Usage

AppVeyor usage is not available.

Cloud Services

GitHub status: No Status Available
Travis CI status: No Status Available
CircleCI status: No Status Available
AppVeyor status: No Status Available
Quay.io status: No Status Available
Azure DevOps: No Status Available

Incidents

2021/11/17 14:53:50 UTC resolved
Builds not running on drone #122
Builds are currently not being triggered on drone which causes native `linux-aarch64` builds to be silently skipped. Cross-compiled and emulated builds are unaffected. We've contacted their support and will update this issue when we know more.
2021/11/09 02:45:29 UTC resolved
CDN cloning backlogged (new packages unavailable) #123
Currently the CDN is having issues cloning. Meaning recently uploaded packages are unavailable. This issue has been raised with Anaconda and is currently being investigated. Will include any status updates here.
2021/10/29 17:00:25 UTC resolved
github actions not running #121
All GitHub Actions in conda-forge repos are not running. We have filed a ticket with GitHub and will update this issue as we learn more. This outage also affects the deployment of this status page so until it's resolved updates can be found at: https://github.com/conda-forge/status/issues/121
2021/10/12 22:11:01 UTC resolved
Travis ppc64 jobs failing with openssl error #120
ref https://app.travis-ci.com/github/conda-forge/awscli-feedstock/jobs/542581068 ``` Validating outputs Cloning into '/tmp/tmpgh5a8gx3_recipe/feedstock-outputs'... fatal: unable to access 'https://github.com/conda-forge/feedstock-outputs.git/': OpenSSL SSL_connect: Connection reset by peer in connection to github.com:443 Traceback (most recent call last): File "/opt/conda/bin/validate_recipe_outputs", line 11, in sys.exit(main()) File "/opt/conda/lib/python3.8/site-packages/click/core.py", line 1126, in __call__ return self.main(*args, **kwargs) File "/opt/conda/lib/python3.8/site-packages/click/core.py", line 1051, in main rv = self.invoke(ctx) File "/opt/conda/lib/python3.8/site-packages/click/core.py", line 1393, in invoke return ctx.invoke(self.callback, **ctx.params) File "/opt/conda/lib/python3.8/site-packages/click/core.py", line 752, in invoke return __callback(*args, **kwargs) File "/opt/conda/lib/python3.8/site-packages/conda_forge_ci_setup/feedstock_outputs.py", line 176, in main results = is_valid_feedstock_output(feedstock_name, built_distributions) File "/opt/conda/lib/python3.8/site-packages/conda_forge_ci_setup/feedstock_outputs.py", line 126, in is_valid_feedstock_output subprocess.run( File "/opt/conda/lib/python3.8/subprocess.py", line 516, in run raise CalledProcessError(retcode, process.args, subprocess.CalledProcessError: Command '['git', 'clone', '--depth=1', 'https://github.com/conda-forge/feedstock-outputs.git', '/tmp/tmpgh5a8gx3_recipe/feedstock-outputs']' returned non-zero exit status 128. The command "if [[ ${PLATFORM} =~ .*linux.* ]]; then ./.scripts/run_docker_build.sh; fi" exited with 1. ``` is this being tracked anywhere else?
2021/08/24 08:44:13 UTC resolved
No CI checks for PRs on feedstocks #117
Since this morning the CI runs don't appear in the checks of PRs on feedstocks. This is affecting all feedstocks I have looked at. See https://github.com/conda-forge/folly-feedstock/pull/1 for an example. The runs themselves still seem to be triggered, see https://dev.azure.com/conda-forge/feedstock-builds/_build.
2021/08/20 12:02:23 UTC resolved
Feedstock conversion from staged-recipes failing #116
Feedstock conversion is currently failing with a permissions error from the Travis CI API. We're in contact with Travis's support and will report back here when more is known.