-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
Adding dismod-at to conda-forge #29516
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Hi! This is the staged-recipes linter and your PR looks excellent! 🚀 |
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 ( I do have some suggestions for making it better though... For recipes/dismod-at/recipe.yaml:
This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/14091017934. Examine the logs at this URL for more detail. |
2025.0.1.path: fix bug in get_option_table.cpp. build.bat: chagne ehco -> echo, bld.bat -> build.bat.
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 ( Here's what I've got... For recipes/dismod-at/recipe.yaml:
For recipes/dismod-at/recipe.yaml:
This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/14092879725. Examine the logs at this URL for more detail. |
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 ( I do have some suggestions for making it better though... For recipes/dismod-at/recipe.yaml:
This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/14271047660. Examine the logs at this URL for more detail. |
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 ( Here's what I've got... For recipes/dismod-at/recipe.yaml:
For recipes/dismod-at/recipe.yaml:
This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/14274063004. Examine the logs at this URL for more detail. |
Co-authored-by: Matthew Feickert <[email protected]>
Co-authored-by: Matthew Feickert <[email protected]>
recipe.yaml: Advance to newer upstream source.
@matthewfeickert The
There also is a The failure is happening during the
So it appears to me that the I do not know why it fails to execute. If you look at the original test file There are some replacements made by |
Do you have a Windows machine that you can test your build on locally? Can you get more verbose output from the failing test? Have you validated that all files needed for your tests are present? |
recipe.yaml: add sqlite3 as a test requirement.
Yes, I have been testing on a windows machine, but just directly building and installing in a temp conda environment. I should try and run the build there and see what happens. Thanks. |
The tests ran successfully using rattler-build on my windows machine. Here is the script I used to run it
|
By
I mean have you been running the |
Where are the instructions for running build-locally.py ?
|
|
The only instructions I found on the page above for building were
This eventually gave the same error as above; i.e. , it does not know were the recipe.yaml is (starting in the staged-recipe.git direcotory). |
Lines 48 to 55 in bbcbafa
oh. I see now that you're also not on a development/feature branch but are on Line 18 in 83e0a2b
In general avoid doing this for any PR and that's going to potentially cause issues for local debugging as it figures out what recipes to build by what differs from |
Now I see the following instructions:
Does it matter what I name the branch ? |
Good question. No, that's totally arbitrary. The internal logic is just that it is comparing the recipes that exist on the source branch to the target branch of Mind you that the build failure in CI is something different though, so if you want to continue to debug here that's fine. Though I might suggest that you ask for advice on the conda-forge Zulip, as I don't know if I can provide anything super actionable.
Another good question. I think this is also arbitrary, as the recipe YAML file and any other supporting files are the only things that matter in the end, but I'm not 100% sure on this. |
…d_prc). run_test.py: use dismod_at.system_command_prc.
Please note the following comment in run_test.py:
You can set skip equal to False and run the test on your local system as a check; see |
@conda-forge/help-python-c, ready for review |
recipes/dismod-at/recipe.yaml
Outdated
@@ -0,0 +1,80 @@ | |||
# conda-verify warnings: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please remove all the comments here. They seem to be quite "empty"
recipes/dismod-at/build.bat
Outdated
%BUILD_PREIX%\Library\lib\pkgconfig;^ | ||
%BUILD_PREIX%\Library\share\pkgconfig; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is not correct. pkg-config should not point to BUILD_PREFIX. Please remove this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
recipe.yaml: remove empty comment.
Checklist
url
) rather than a repo (e.g.git_url
) is used in your recipe (see here for more details).