Skip to content

Conversation

@SylvainCorlay
Copy link
Member

@SylvainCorlay SylvainCorlay commented Apr 10, 2020

The appveyor build was timing out. Not bumping the build number since the windows build for the current number was never uploaded.

Checklist

@conda-forge-linter
Copy link

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

I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.

Here's what I've got...

For recipe:

  • Failed to even lint the recipe, probably because of a conda-smithy bug 😢. This likely indicates a problem in your meta.yaml, though. To get a traceback to help figure out what's going on, install conda-smithy and run conda smithy recipe-lint . from the recipe directory.

@conda-forge-linter
Copy link

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.

@jjhelmus
Copy link
Contributor

The Visual Studio install on Azure Pipelines does not have the necessary bits for PGO. This might work if PGO is disabled by removing --pgo from line 19 of bld.bat.

An attempt was bade in #275 to build with Azure without success.

@jjhelmus
Copy link
Contributor

Disabling PGO on Windows works. Is this reasonable for the other maintains or should we look for another solution?

@SylvainCorlay
Copy link
Member Author

I don't know much about PGO.

@isuruf isuruf closed this Aug 17, 2021
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.

4 participants