Skip to content

Commit

Permalink
Merge pull request #1 from regro-cf-autotick-bot/rebuild-pypy-0-1_h82…
Browse files Browse the repository at this point in the history 
…87bf

Rebuild for pypy
  • Loading branch information
@mariusvniekerk
mariusvniekerk committed Sep 23, 2020
2 parents 6c14f43 + 3633178 commit a3f4087
Show file tree
Hide file tree
Showing 7 changed files with 95 additions and 1 deletion.
4 changes: 4 additions & 0 deletions .azure-pipelines/azure-pipelines-linux.yml
View file

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

3 changes: 3 additions & 0 deletions .azure-pipelines/azure-pipelines-osx.yml
View file

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

14 changes: 14 additions & 0 deletions .ci_support/linux_64_python3.6.____73_pypy.yaml
View file
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
channel_sources:
- conda-forge,defaults
channel_targets:
- conda-forge main
docker_image:
- condaforge/linux-anvil-comp7
pin_run_as_build:
python:
min_pin: x.x
max_pin: x.x
python:
- 3.6.* *_73_pypy
target_platform:
- linux-64
43 changes: 43 additions & 0 deletions .ci_support/migrations/pypy.yaml
View file
Original file line number Diff line number Diff line change
@@ -0,0 +1,43 @@
migrator_ts: 1580746218 # The timestamp of when the migration was made
__migrator:
kind:
version
exclude:
- c_compiler
- vc
- cxx_compiler
- cuda_compiler_version
- docker_image
migration_number: # Only use this if the bot messes up, putting this in will cause a complete rerun of the migration
1
bump_number: 1 # Hashes changed for cpython, so it's better to bump build numbers.
# do not use mamba to check if the issued PRs are solvable
check_solvable: false

python:
- 3.6.* *_cpython # [not (osx and arm64)]
- 3.7.* *_cpython # [not (osx and arm64)]
- 3.8.* *_cpython
- 3.6.* *_73_pypy # [not (win64 or (osx and arm64))]

numpy:
- 1.16 # [not (osx and arm64)]
- 1.16 # [not (osx and arm64)]
- 1.16
- 1.18 # [not (win64 or (osx and arm64))]

python_impl:
- cpython # [not (osx and arm64)]
- cpython # [not (osx and arm64)]
- cpython
- pypy # [not (win64 or (osx and arm64))]


zip_keys:
-
- python
- numpy
- python_impl
- # [linux64]
- cuda_compiler_version # [linux64]
- docker_image # [linux64]
16 changes: 16 additions & 0 deletions .ci_support/osx_64_python3.6.____73_pypy.yaml
View file
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
MACOSX_DEPLOYMENT_TARGET:
- '10.9'
channel_sources:
- conda-forge,defaults
channel_targets:
- conda-forge main
macos_machine:
- x86_64-apple-darwin13.4.0
pin_run_as_build:
python:
min_pin: x.x
max_pin: x.x
python:
- 3.6.* *_73_pypy
target_platform:
- osx-64
14 changes: 14 additions & 0 deletions README.md
View file

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion recipe/meta.yaml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ source:
sha256: b39ee72de945cd6be3dcd14939e49d70fdaaad6230dea7363e82e7d4eda67661

build:
number: 0
number: 1
skip: true # [py2k]
script: {{ PYTHON }} -m pip install . -vv

Expand Down

11 comments on commit a3f4087

@conda-forge-linter
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @conda-forge/opentelemetry-api! This is the friendly automated conda-forge-webservice!

It appears that one or more of your feedstock's outputs did not copy from the
staging channel to the conda-forge production channels. :(

This failure can happen for a lot of reasons, including an outdated feedstock
token. Below we have put some information about the failure to help you debug it.

If you have any issues or questions, you can find us on gitter in the
community chat room or you can bump us right in this comment.

error messages:

  • invalid copy request (either bad data or bad feedstock token)

@conda-forge-linter
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @conda-forge/opentelemetry-api! This is the friendly automated conda-forge-webservice!

It appears that one or more of your feedstock's outputs did not copy from the
staging channel to the conda-forge production channels. :(

This failure can happen for a lot of reasons, including an outdated feedstock
token. Below we have put some information about the failure to help you debug it.

If you have any issues or questions, you can find us on gitter in the
community chat room or you can bump us right in this comment.

error messages:

  • invalid copy request (either bad data or bad feedstock token)

@conda-forge-linter
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @conda-forge/opentelemetry-api! This is the friendly automated conda-forge-webservice!

It appears that one or more of your feedstock's outputs did not copy from the
staging channel to the conda-forge production channels. :(

This failure can happen for a lot of reasons, including an outdated feedstock
token. Below we have put some information about the failure to help you debug it.

If you have any issues or questions, you can find us on gitter in the
community chat room or you can bump us right in this comment.

error messages:

  • invalid copy request (either bad data or bad feedstock token)

@conda-forge-linter
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @conda-forge/opentelemetry-api! This is the friendly automated conda-forge-webservice!

It appears that one or more of your feedstock's outputs did not copy from the
staging channel to the conda-forge production channels. :(

This failure can happen for a lot of reasons, including an outdated feedstock
token. Below we have put some information about the failure to help you debug it.

If you have any issues or questions, you can find us on gitter in the
community chat room or you can bump us right in this comment.

error messages:

  • invalid copy request (either bad data or bad feedstock token)

@conda-forge-linter
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @conda-forge/opentelemetry-api! This is the friendly automated conda-forge-webservice!

It appears that one or more of your feedstock's outputs did not copy from the
staging channel to the conda-forge production channels. :(

This failure can happen for a lot of reasons, including an outdated feedstock
token. Below we have put some information about the failure to help you debug it.

If you have any issues or questions, you can find us on gitter in the
community chat room or you can bump us right in this comment.

error messages:

  • invalid copy request (either bad data or bad feedstock token)

@conda-forge-linter
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @conda-forge/opentelemetry-api! This is the friendly automated conda-forge-webservice!

It appears that one or more of your feedstock's outputs did not copy from the
staging channel to the conda-forge production channels. :(

This failure can happen for a lot of reasons, including an outdated feedstock
token. Below we have put some information about the failure to help you debug it.

If you have any issues or questions, you can find us on gitter in the
community chat room or you can bump us right in this comment.

error messages:

  • invalid copy request (either bad data or bad feedstock token)

@conda-forge-linter
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @conda-forge/opentelemetry-api! This is the friendly automated conda-forge-webservice!

It appears that one or more of your feedstock's outputs did not copy from the
staging channel to the conda-forge production channels. :(

This failure can happen for a lot of reasons, including an outdated feedstock
token. Below we have put some information about the failure to help you debug it.

If you have any issues or questions, you can find us on gitter in the
community chat room or you can bump us right in this comment.

error messages:

  • invalid copy request (either bad data or bad feedstock token)

@conda-forge-linter
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @conda-forge/opentelemetry-api! This is the friendly automated conda-forge-webservice!

It appears that one or more of your feedstock's outputs did not copy from the
staging channel to the conda-forge production channels. :(

This failure can happen for a lot of reasons, including an outdated feedstock
token. Below we have put some information about the failure to help you debug it.

If you have any issues or questions, you can find us on gitter in the
community chat room or you can bump us right in this comment.

error messages:

  • invalid copy request (either bad data or bad feedstock token)

@conda-forge-linter
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @conda-forge/opentelemetry-api! This is the friendly automated conda-forge-webservice!

It appears that one or more of your feedstock's outputs did not copy from the
staging channel to the conda-forge production channels. :(

This failure can happen for a lot of reasons, including an outdated feedstock
token. Below we have put some information about the failure to help you debug it.

If you have any issues or questions, you can find us on gitter in the
community chat room or you can bump us right in this comment.

error messages:

  • invalid copy request (either bad data or bad feedstock token)

@conda-forge-linter
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @conda-forge/opentelemetry-api! This is the friendly automated conda-forge-webservice!

It appears that one or more of your feedstock's outputs did not copy from the
staging channel to the conda-forge production channels. :(

This failure can happen for a lot of reasons, including an outdated feedstock
token. Below we have put some information about the failure to help you debug it.

If you have any issues or questions, you can find us on gitter in the
community chat room or you can bump us right in this comment.

error messages:

  • invalid copy request (either bad data or bad feedstock token)

@conda-forge-linter
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @conda-forge/opentelemetry-api! This is the friendly automated conda-forge-webservice!

It appears that one or more of your feedstock's outputs did not copy from the
staging channel to the conda-forge production channels. :(

This failure can happen for a lot of reasons, including an outdated feedstock
token. Below we have put some information about the failure to help you debug it.

If you have any issues or questions, you can find us on gitter in the
community chat room or you can bump us right in this comment.

error messages:

  • invalid copy request (either bad data or bad feedstock token)

Please sign in to comment.