cupy v8.2.0

[regro-cf-autotick-bot]

It is very likely that the current package version for this feedstock is out of date. Notes for merging 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. 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

Note that 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.

NEW: If you want these PRs to be merged automatically, make an issue with code>@conda-forge-admin,</codeplease add bot automerge in the title and merge the resulting PR. This command will add our new bot automerge feature to your feedstock!

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 code>@<space/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. If you would like a local version of this bot, you might consider using rever. Rever is a tool for automating software releases and forms the backbone of the bot's conda-forge PRing capability. Rever is both conda (conda install -c conda-forge rever) and pip (pip install re-ver) installable. Finally, feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/autotick-bot/actions/runs/384704315, please use this URL for debugging}

Dependency Analysis

We couldn't run dependency analysis due to an internal error in the bot. :( Help is very welcome!

[conda-forge-linter]

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

[toslunar]

compiler version issue?

    RuntimeError: Encountered unknown error while testing nvcc:
    In file included from /usr/local/cuda/bin/../targets/x86_64-linux/include/cuda_runtime.h:83,
                     from <command-line>:
    /usr/local/cuda/bin/../targets/x86_64-linux/include/crt/host_config.h:138:2: error: #error -- unsupported GNU version! gcc versions later than 8 are not supported!
      138 | #error -- unsupported GNU version! gcc versions later than 8 are not supported!
          |  ^~~~~

[leofang]

Yes, I think this is due to the compiler migration on Conda-Forge, see the 2020-10-08 entry in the announcement https://conda-forge.org/docs/user/announcements.html. Looks like the global pinning has been updated to gcc9.

@jakirkham I am hoping that by resolving https://github.com/conda-forge/nvcc-feedstock/issues/51 this issue can be fixed without us changing anything in this feedstock. Do you think it could happen anytime soon?

[leofang]

@conda-forge-admin, please rerender

[github-actions[bot]]

Hi! This is the friendly automated conda-forge-webservice. I tried to rerender for you, but it looks like there was nothing to do.

[leofang]

Kicking off the bot again to see if the compiler issue is resolved or not...

[leofang]

@conda-forge-admin, please rerender

[leofang]

@conda-forge-admin, please rerender

[conda-forge-linter]

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

I was trying to look for recipes to lint for you, but it appears we have a merge conflict. Please try to merge or rebase with the base branch to resolve this conflict.

Please ping the 'conda-forge/core' team (using the @ notation in a comment) if you believe this is a bug.

[regro-cf-autotick-bot]

I see that this PR has conflicts and I'm the only committer I'm going to close this PR and will make another one as appropriate. This was generated by

[leofang]

wtf...

[jakirkham]

My guess is the changes made to conda-forge-pinning resulted in changes here. So the bot closed it out and is regenerating the PR. That’s only a guess though