search

conda-forge / openmpi-feedstock

A conda-smithy repository for openmpi.
BSD 3-Clause "New" or "Revised" License
9 stars 22 forks source link

Rebuild for windows_cuda #70

Closed regro-cf-autotick-bot closed 3 years ago

regro-cf-autotick-bot commented 3 years ago

This PR has been triggered in an effort to update windows_cuda.

Notes and instructions for merging this PR:

  1. Please merge the PR only after the tests have passed.
  2. Feel free to push to the bot's branch to update this PR if needed.

Please note that if you close this PR we presume that the feedstock has been rebuilt, so if you are going to perform the rebuild yourself don't close this PR until the your rebuild has been merged.

This package has the following downstream children:

And potentially more.

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/382290290, please use this URL for debugging

conda-forge-linter commented 3 years ago

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.

dalcinl commented 3 years ago

@leofang Many builds failed in once this was merged to master. Not getting notifications about these failures is annoying, but you have to remember to check back the status of your merge, or you end up with missing packages. Right now I have a PETSc update PR with failures for the Open MPI case, although I don't know the failures are related to the partial building of this PR.

@isuruf Is there any way to get notifications when CI fails after merging a PR into to master? Am I missing some notification setting?

isuruf commented 3 years ago

@dalcinl, there's probably a way to do that, but I'm not sure how to enable it. I don't receive them either.

leofang commented 3 years ago

@dalcinl I don't get it. What are the failures that you're referring to? The check on master is green:

截圖 2020-12-06 上午3 33 40

and when I clicked the links in the check to the CIs, everything looks fine to me. Could you list the failures here (with links) so that people can help?

Recently there're many migration works happening in parallel, so it could be a bit hard to pinpoint which one is the trouble maker.

dalcinl commented 3 years ago

@dalcinl I don't get it. What are the failures that you're referring to?

Of course you do not get it now :-) All the failures were network errors and things like that. I restarted all the failed builds manually, and now all is green. This will happen again, to any of us.

beckermr commented 3 years ago

We can likely use github actions to listen for failed CI events on master and make issues reporting them. We could also have the heroku server do this.

I'm happy to help guide someone if they want to implement this.

leofang commented 3 years ago

I don't get it. What are the failures that you're referring to?

Of course you do not get it now :-) All the failures were network errors and things like that. I restarted all the failed builds manually, and now all is green. This will happen again, to any of us.

Ouch, sorry @dalcinl. Thanks for resolving it...