Skip to content

pyamrex v26.04#63

Merged
ax3l merged 11 commits intoconda-forge:mainfrom
regro-cf-autotick-bot:26.04_h38c562
Apr 8, 2026
Merged

pyamrex v26.04#63
ax3l merged 11 commits intoconda-forge:mainfrom
regro-cf-autotick-bot:26.04_h38c562

Conversation

@regro-cf-autotick-bot
Copy link
Copy Markdown
Contributor

It is very likely that the current package version for this feedstock is out of date.

Checklist before merging this PR:

  • Dependencies have been updated if changed: see upstream
  • Tests have passed
  • Updated license if changed and license_file is packaged

Information about this PR:

  1. Feel free to push to the bot's branch to update this PR if needed.
  2. The bot will almost always only open one PR per version.
  3. The bot will stop issuing PRs if more than 3 version bump PRs generated by the bot are open. If you don't want to package a particular version please close the PR.
  4. If you want these PRs to be merged automatically, make an issue with @conda-forge-admin,please add bot automerge in the title and merge the resulting PR. This command will add our bot automerge feature to your feedstock.
  5. If this PR was opened in error or needs to be updated please add the bot-rerun label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase @conda-forge-admin, please rerun bot in a PR comment to have the conda-forge-admin add it for you.

This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. Feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/cf-scripts/actions/runs/23964116462 - please use this URL for debugging.

@conda-forge-admin
Copy link
Copy Markdown
Contributor

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/recipe.yaml) and found it was in an excellent condition.

@ax3l
Copy link
Copy Markdown
Member

ax3l commented Apr 4, 2026

We need to patch AMReX first (version in changes file): conda-forge/amrex-feedstock#78

@ax3l ax3l closed this Apr 6, 2026
@ax3l ax3l reopened this Apr 6, 2026
@EZoni
Copy link
Copy Markdown
Member

EZoni commented Apr 6, 2026

@conda-forge-admin, please rerender

Comment on lines +1 to +5
python:
- 3.11
- 3.12
- 3.13
- 3.14
Copy link
Copy Markdown
Member

@EZoni EZoni Apr 6, 2026

Choose a reason for hiding this comment

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

Added this because Python must be 3.11+ since pyAMReX 26.03 (https://github.com/AMReX-Codes/pyamrex/releases/tag/26.03).

The previous commit e39f51f raised errors like the following:

ERROR: Package 'amrex' requires a different Python: 3.10.20 not in '>=3.11'

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

This breaks the automatic rerendering, see from https://github.com/conda-forge/conda-forge-webservices/actions/runs/24052856620/job/70152392549:

Traceback (most recent call last):
  File "/opt/conda/envs/cf-feedstock-ops/bin/conda-smithy", line 10, in <module>
    sys.exit(main())
             ^^^^^^
  File "/opt/conda/envs/cf-feedstock-ops/lib/python3.12/site-packages/conda_smithy/cli.py", line 760, in main
    args.subcommand_func(args)
  File "/opt/conda/envs/cf-feedstock-ops/lib/python3.12/site-packages/conda_smithy/cli.py", line 610, in __call__
    self._call(args, args.temporary_directory)
  File "/opt/conda/envs/cf-feedstock-ops/lib/python3.12/site-packages/conda_smithy/cli.py", line 613, in _call
    configure_feedstock.main(
  File "/opt/conda/envs/cf-feedstock-ops/lib/python3.12/site-packages/conda_smithy/configure_feedstock.py", line 3019, in main
    render_info.append(render_azure(env, config, forge_dir, return_metadata=True))
                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/conda/envs/cf-feedstock-ops/lib/python3.12/site-packages/conda_smithy/configure_feedstock.py", line 2049, in render_azure
    return _render_ci_provider(
           ^^^^^^^^^^^^^^^^^^^^
  File "/opt/conda/envs/cf-feedstock-ops/lib/python3.12/site-packages/conda_smithy/configure_feedstock.py", line 1290, in _render_ci_provider
    migrated_combined_variant_spec = migrate_combined_spec(
                                     ^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/conda/envs/cf-feedstock-ops/lib/python3.12/site-packages/conda_smithy/configure_feedstock.py", line 1115, in migrate_combined_spec
    combined_spec = variant_add(combined_spec, migration)
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/conda/envs/cf-feedstock-ops/lib/python3.12/site-packages/conda_smithy/variant_algebra.py", line 315, in variant_add
    return VARIANT_OP[operation](v1, v2)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/conda/envs/cf-feedstock-ops/lib/python3.12/site-packages/conda_smithy/variant_algebra.py", line 230, in op_variant_key_add
    all_tuples = sorted(all_tuples_unsorted, key=sorter)
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/conda/envs/cf-feedstock-ops/lib/python3.12/site-packages/conda_smithy/variant_algebra.py", line 227, in <lambda>
    sorter = lambda x: _version_order(
                       ^^^^^^^^^^^^^^^
  File "/opt/conda/envs/cf-feedstock-ops/lib/python3.12/site-packages/conda_smithy/variant_algebra.py", line 63, in _version_order
    return ordering.index(v)
           ^^^^^^^^^^^^^^^^^
ValueError: '3.11' is not in list

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Trying the skip directive in recipe/recipe.yaml instead in 69ba436.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

There should be a field python that can be used for min version in recipe

Copy link
Copy Markdown
Member

@EZoni EZoni Apr 6, 2026

Choose a reason for hiding this comment

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

I see. Maybe this will work:

diff --git a/recipe/recipe.yaml b/recipe/recipe.yaml
index 3e2dd46..36b5209 100644
--- a/recipe/recipe.yaml
+++ b/recipe/recipe.yaml
@@ -8,6 +8,7 @@ context:
   build: 0
   mpi: ${{ mpi or "nompi" }}  # is this still needed?
   mpi_prefix: ${{ "nompi" if mpi == "nompi" else "mpi_" + mpi }}
+  python_min: "3.11"
 
 package:
   name: ${{ name|lower }}
@@ -18,7 +19,7 @@ source:
   sha256: 0d17f27ca7463b9983a987629ea2c18e06a8e4d98b2b8c6affb7aacfe340690d
 
 build:
-  skip: python_impl == "pypy" or python == "3.10.* *_cpython"
+  skip: python_impl == "pypy"
   # add build string so packages can depend on
   # mpi or nompi variants
   # dependencies:
@@ -61,13 +62,11 @@ requirements:
     - amrex >=${{ version }}[build=${{ mpi_prefix }}_${{ pyamrex_precision }}_*]
     - if: "mpi != 'nompi'"
       then: ${{ mpi }}
-    - python
-    - pybind11
     - numpy
     - pip
     - pybind11
     - pybind11-abi
-    - python
+    - python ${{ python_min }}.*
     - setuptools
     - vir-simd
     - wheel
@@ -77,7 +76,7 @@ requirements:
       then:
         - ${{ mpi }}
         - mpi4py
-    - python
+    - python >=${{ python_min }}
     - if: osx
       then: libcxx
   run_exports:
@@ -92,6 +91,7 @@ tests:
       imports:
         - amrex
       pip_check: false
+      python_version: ${{ python_min }}.*
   - script:
       - if: win
         then: set "OMP_NUM_THREADS=2"

Note this also removes duplicate entries (python and pybind11).

Copy link
Copy Markdown
Member

@ax3l ax3l Apr 6, 2026

Choose a reason for hiding this comment

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

python_min might usually need to go into the build config file in the root of the repo, would need to check

Oops, I deleted my comment with nice links into the CF knowledge base by accident.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

On the other hand we had a lot of Python 3.10 builds in these PR's CI checks (see e39f51f), so I don't see how that's excluded by default. So we do need to do something about it, no?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Yes that makes sense. I thought CF had already migrated as in earlier versions

@conda-forge-admin
Copy link
Copy Markdown
Contributor

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you but ran into some issues. Please check the output logs of the GitHub Actions workflow below for more details. You can also ping conda-forge/core (using the @ notation) for further assistance or you can try rerendering locally.

The following suggestions might help debug any issues:

  • Is the recipe/{meta.yaml,recipe.yaml} file valid?
  • If there is a recipe/conda-build-config.yaml file in the feedstock make sure that it is compatible with the current global pinnings.
  • Is the fork used for this PR on an organization or user GitHub account? Automated rerendering via the webservices admin bot only works for user GitHub accounts.

This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/24052856620. Examine the logs at this URL for more detail.

@EZoni
Copy link
Copy Markdown
Member

EZoni commented Apr 6, 2026

@conda-forge-admin, please rerender

EZoni added 2 commits April 7, 2026 10:23
…6.04.07.10.45.57

Other tools:
- conda-build 26.3.0
- rattler-build 0.61.4
- rattler-build-conda-compat 1.4.11
Copy link
Copy Markdown
Member

@matthewfeickert matthewfeickert left a comment

Choose a reason for hiding this comment

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

@conda-forge/pyamrex note also that if you use the following conda-forge.yml you get native linux-aarch64 and osx-arm64 builds (also Pixi support). For linux-ppc64le you don't need to repeat the key in the provider as build_platform allows for cross-compile and then the linux-* to linux-* emulation in testing doesn't need an explicit provider to be defined.

build_platform:
  linux_ppc64le: linux_64
conda_build:
  error_overlinking: true
  pkg_format: '2'
conda_build_tool: rattler-build
conda_install_tool: pixi
conda_forge_output_validation: true
github:
  branch_name: main
  tooling_branch_name: main
provider:
  linux_aarch64: default
  osx_arm64: default
  win: default
test: native_and_emulated

ax3l and others added 3 commits April 7, 2026 14:11
Co-authored-by: Matthew Feickert <matthew.feickert@cern.ch>
Co-authored-by: Matthew Feickert <matthew.feickert@cern.ch>
@ax3l
Copy link
Copy Markdown
Member

ax3l commented Apr 7, 2026

@conda-forge-admin, please rerender

@matthewfeickert
Copy link
Copy Markdown
Member

@ax3l you might want to poke it again or just locally rerender with

pixi exec conda-smithy regenerate -c

as I think it just got stuck.

@EZoni
Copy link
Copy Markdown
Member

EZoni commented Apr 7, 2026

I don't understand why we still see Python 3.10 builds, nor do I understand why they pass now.

@matthewfeickert
Copy link
Copy Markdown
Member

matthewfeickert commented Apr 7, 2026

I don't understand why we still see Python 3.10 builds,

Because the feedstock hasn't been rerendered. @ax3l posted requests like #63 (comment) multiple times in a row while making pushes and I think the bot got confused and never finished the conda-smithy operations. Hence my comment #63 (comment).

I also just rerender locally with the commands I've been posting as it is way faster and makes the PR not as noisy.

nor do I understand why they pass now.

Because they are starting and then immediately having the build be skipped. So they are no-ops.

@EZoni
Copy link
Copy Markdown
Member

EZoni commented Apr 7, 2026

@conda-forge-admin, please rerender

…6.04.07.10.45.57

Other tools:
- conda-build 26.3.0
- rattler-build 0.61.4
- rattler-build-conda-compat 1.4.11
@matthewfeickert
Copy link
Copy Markdown
Member

matthewfeickert commented Apr 7, 2026

Hm. Maybe there's a conda-forge bot bug, as looking at the bot CI run that @EZoni initiated: https://github.com/conda-forge/conda-forge-webservices/actions/runs/24109602658 I can see in the finalize-task logs

[26.04_h38c562 e2d3667] MNT: Re-rendered with conda-smithy 3.58.1 and conda-forge-pinning 2026.04.07.10.45.5
 169 files changed, 1004 insertions(+), 2259 deletions(-)
 delete mode 100755 .azure-pipelines/azure-pipelines-win.yml
 delete mode 100644 .ci_support/linux_64_mpimpichpyamrex_precisiondppython3.10.____cpython.yaml
 delete mode 100644 .ci_support/linux_64_mpimpichpyamrex_precisionsppython3.10.____cpython.yaml
 delete mode 100644 .ci_support/linux_64_mpinompipyamrex_precisiondppython3.10.____cpython.yaml
 delete mode 100644 .ci_support/linux_64_mpinompipyamrex_precisionsppython3.10.____cpython.yaml
 delete mode 100644 .ci_support/linux_64_mpiopenmpipyamrex_precisiondppython3.10.____cpython.yaml
 delete mode 100644 .ci_support/linux_64_mpiopenmpipyamrex_precisionsppython3.10.____cpython.yaml
 delete mode 100644 .ci_support/linux_aarch64_mpimpichpyamrex_precisiondppython3.10.____cpython.yaml
 delete mode 100644 .ci_support/linux_aarch64_mpimpichpyamrex_precisionsppython3.10.____cpython.yaml
 delete mode 100644 .ci_support/linux_aarch64_mpinompipyamrex_precisiondppython3.10.____cpython.yaml
 delete mode 100644 .ci_support/linux_aarch64_mpinompipyamrex_precisionsppython3.10.____cpython.yaml
 delete mode 100644 .ci_support/linux_aarch64_mpiopenmpipyamrex_precisiondppython3.10.____cpython.yaml
 delete mode 100644 .ci_support/linux_aarch64_mpiopenmpipyamrex_precisionsppython3.10.____cpython.yaml
 delete mode 100644 .ci_support/linux_ppc64le_mpimpichpyamrex_precisiondppython3.10.____cpython.yaml
 delete mode 100644 .ci_support/linux_ppc64le_mpimpichpyamrex_precisionsppython3.10.____cpython.yaml
 delete mode 100644 .ci_support/linux_ppc64le_mpinompipyamrex_precisiondppython3.10.____cpython.yaml
 delete mode 100644 .ci_support/linux_ppc64le_mpinompipyamrex_precisionsppython3.10.____cpython.yaml
 delete mode 100644 .ci_support/linux_ppc64le_mpiopenmpipyamrex_precisiondppython3.10.____cpython.yaml
 delete mode 100644 .ci_support/linux_ppc64le_mpiopenmpipyamrex_precisionsppython3.10.____cpython.yaml
 delete mode 100644 .ci_support/osx_64_mpimpichpyamrex_precisiondppython3.10.____cpython.yaml
 delete mode 100644 .ci_support/osx_64_mpimpichpyamrex_precisionsppython3.10.____cpython.yaml
 delete mode 100644 .ci_support/osx_64_mpinompipyamrex_precisiondppython3.10.____cpython.yaml
 delete mode 100644 .ci_support/osx_64_mpinompipyamrex_precisionsppython3.10.____cpython.yaml
 delete mode 100644 .ci_support/osx_64_mpiopenmpipyamrex_precisiondppython3.10.____cpython.yaml
 delete mode 100644 .ci_support/osx_64_mpiopenmpipyamrex_precisionsppython3.10.____cpython.yaml
 delete mode 100644 .ci_support/osx_arm64_mpimpichpyamrex_precisiondppython3.10.____cpython.yaml
 delete mode 100644 .ci_support/osx_arm64_mpimpichpyamrex_precisionsppython3.10.____cpython.yaml
 delete mode 100644 .ci_support/osx_arm64_mpinompipyamrex_precisiondppython3.10.____cpython.yaml
 delete mode 100644 .ci_support/osx_arm64_mpinompipyamrex_precisionsppython3.10.____cpython.yaml
 delete mode 100644 .ci_support/osx_arm64_mpiopenmpipyamrex_precisiondppython3.10.____cpython.yaml
 delete mode 100644 .ci_support/osx_arm64_mpiopenmpipyamrex_precisionsppython3.10.____cpython.yaml
 delete mode 100644 .ci_support/win_64_pyamrex_precisiondppython3.10.____cpython.yaml
 delete mode 100644 .ci_support/win_64_pyamrex_precisionsppython3.10.____cpython.yaml
 create mode 100644 pixi.toml
INFO:conda_forge_webservices.github_actions_integration.utils:pushing and commenting: branch|owner|repo = 26.04_h38c562|regro-cf-autotick-bot|pyamrex-feedstock
WARNING:git.remote:Error lines received while fetching: error: failed to push some refs to 'https://github.com/regro-cf-autotick-bot/pyamrex-feedstock.git'

edit: Reported in conda-forge/conda-forge-webservices#1300.

@EZoni
Copy link
Copy Markdown
Member

EZoni commented Apr 7, 2026

I pushed the result of #63 (comment) in fd2b25d, because the conda-forge bot trigger did not seem to have a net effect. Locally it seems to be consistent with what was observed in #63 (comment), in terms of git diff and files removed. Let's see if it worked.

@ax3l
Copy link
Copy Markdown
Member

ax3l commented Apr 8, 2026

Yay, thank you both for the great help!

@ax3l ax3l merged commit 99f2e26 into conda-forge:main Apr 8, 2026
131 checks passed
@regro-cf-autotick-bot regro-cf-autotick-bot deleted the 26.04_h38c562 branch April 8, 2026 07:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants