Skip to content

Rebuild for aws_c_startofaugust26 - #2056

Open
xhochy wants to merge 2 commits into
conda-forge:mainfrom
xhochy:aws_c_startofaugust26
Open

xhochy wants to merge 2 commits into
conda-forge:mainfrom
xhochy:aws_c_startofaugust26

Conversation

@xhochy

@xhochy xhochy commented Sep 24, 2026

Copy link
Copy Markdown
Member

The bot has skipped this.

…2026.09.24.04.24.45

Other tools:
- conda-build 26.7.1
- rattler-build 0.76.1
- rattler-build-conda-compat 1.4.19
@xhochy

xhochy commented Sep 24, 2026

Copy link
Copy Markdown
Member Author

Once successful, I would make the PRs for the older versions.

@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/meta.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipe/meta.yaml:

  • ℹ️ The recipe is not parsable by parser conda-souschef (grayskull). This parser is not currently used by conda-forge, but may be in the future. We are collecting information to see which recipes are compatible with grayskull.
  • ℹ️ The recipe is not parsable by parser conda-recipe-manager. The recipe can only be automatically migrated to the new v1 format if it is parseable by conda-recipe-manager.

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

@h-vetinari h-vetinari left a comment

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.

Thanks

@h-vetinari h-vetinari added the automerge Merge the PR when CI passes label Sep 24, 2026
@conda-forge-admin

Copy link
Copy Markdown
Contributor

Hi! This is the friendly conda-forge automerge bot!

I considered the following status checks when analyzing this PR:

  • linter: passed
  • azure: passed
  • github-actions: failed

Thus the PR was not passing and not merged.

@h-vetinari

Copy link
Copy Markdown
Member

I think this is apache/arrow#50845

@h-vetinari

Copy link
Copy Markdown
Member

See also #2054 & #2050

@xhochy

xhochy commented Sep 25, 2026

Copy link
Copy Markdown
Member Author

@h-vetinari Do you have a preferred way forward here? I don't think we're able to fix this by ourselves. Nor do I know how we could provide additional information.

@h-vetinari

Copy link
Copy Markdown
Member

I guess we can skip that test on windows... Or try to help get some of the traces/logs that upstream asked for

@h-vetinari

Copy link
Copy Markdown
Member

There's also apache/arrow#50085 to consider, but I'd like avoiding such a big hammer as building grpc with GPR_DISABLE_ABSEIL_SYNC

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automerge Merge the PR when CI passes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants