staged-recipes: Master is failing to create the feedstocks

CI support files regenerated. These need to be pushed to github!
[master 6f53a0b] Re-render the feedstock after CI registration.
 2 files changed, 7 insertions(+), 7 deletions(-)
 rewrite conda-forge.yml (85%)
rm 'recipes/check/build.sh'
rm 'recipes/check/meta.yaml'
CI Summary for conda-forge/libmo_unpack-feedstock (can take ~30s):
 * conda-forge/libmo_unpack-feedstock already enabled on travis-ci
 * conda-forge/libmo_unpack-feedstock already enabled on CircleCI
 * conda-forge/libmo_unpack-feedstock already enabled on appveyor
Traceback (most recent call last):
  File "/Users/travis/miniconda/bin/conda-smithy", line 9, in <module>
    load_entry_point('conda-smithy==0.7.1', 'console_scripts', 'conda-smithy')()
  File "/Users/travis/miniconda/lib/python2.7/site-packages/conda_smithy/cli.py", line 227, in main
    args.subcommand_func(args)
  File "/Users/travis/miniconda/lib/python2.7/site-packages/conda_smithy/cli.py", line 162, in __call__
    ci_register.appveyor_configure(owner, repo)
  File "/Users/travis/miniconda/lib/python2.7/site-packages/conda_smithy/ci_register.py", line 114, in appveyor_configure
    raise ValueError(response)
ValueError: <Response [404]>
Traceback (most recent call last):
  File ".CI/create_feedstocks.py", line 123, in <module>
    subprocess.check_call(['conda', 'smithy', 'register-ci', '--feedstock_directory', feedstock_dir] + owner_info)
  File "/Users/travis/miniconda/lib/python2.7/subprocess.py", line 540, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['conda', 'smithy', 'register-ci', '--feedstock_directory', '/var/folders/gw/_2jq29095y7b__wtby9dg_5h0000gn/T/tmpmtorVK__feedstocks/libmo_unpack-feedstock', '--organization', 'conda-forge']' returned non-zero exit status 1

About this issue

  • Original URL
  • State: closed
  • Created 8 years ago
  • Reactions: 1
  • Comments: 22 (22 by maintainers)

Most upvoted comments

Yeah, I think you’re right. Sorry, we can’t get it in yet. Maybe you can save a PR to re-add once we get this sorted.

The dependencies were upload and the libmo-unpack build is working. But AppVeyor’s registration is not.

The URL that is 404ing is https://ci.appveyor.com/api/projects/{}/{}/settings and that should resolve to https://ci.appveyor.com/api/projects/conda-forge/libmo-unpack-feedstock/settings, which is fine BTW.

However, something is amiss. And the problem is…

libmo_unpack vs libmo-unpack! I hate underscores and dash issues 😒

@jakirkham I think I know what is going on and I am working on it. Please hold the merges a little bit.

Let’s hold off merging stuff until we figure this out.