You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@CJ-Wright - to my knowledge there is no test suite in fox-objcryst (the source project)
However, it would be still useful to have at least a simple test compilation in the recipe.
Can you have a crack on transferring the travis test (under the script: section) to conda-recipe?
You may need to add a test: source_files: section to meta.yaml to have the examples/testlib.cpp available during the test.
I saw those tests. Nice. Can we work to close this? Presumably if the tests run automatically they will be run by the CF build. What needs to be done to activate this last step?
I took a look and it looks as if we don't handle the libojcryst releases. They have all been done manually by @vincefn.
If you like we can roll them into our release structure, or you can continue to handle them. We would have to run scikit-package on the directory to build those workflows and store them, but it shouldn't break anything. Just let us know.
Activity
Avoid situations when no Crystal structure is chosen and an auto-Le B…
pavoljuhas commentedon Apr 20, 2017
@CJ-Wright - to my knowledge there is no test suite in fox-objcryst (the source project)
However, it would be still useful to have at least a simple test compilation in the recipe.
Can you have a crack on transferring the travis test (under the
script:section) to conda-recipe?You may need to add a
test: source_files:section to meta.yaml to have the examples/testlib.cpp available during the test.CJ-Wright commentedon Apr 21, 2017
I won't be able to do this in the near future, but I eventually will be able to take a look into it.
pavoljuhas commentedon Apr 21, 2017
That's fine, it is not too urgent.
vincefn commentedon Aug 8, 2026
tests have been added by #31 - not integrated into the conda recipe yet
sbillinge commentedon Aug 15, 2026
I saw those tests. Nice. Can we work to close this? Presumably if the tests run automatically they will be run by the CF build. What needs to be done to activate this last step?
vincefn commentedon Aug 17, 2026
Not sure what's still needed, and also whether this is for the internal conda build, or for the conda-forge one.
sbillinge commentedon Aug 25, 2026
I took a look and it looks as if we don't handle the libojcryst releases. They have all been done manually by @vincefn.
If you like we can roll them into our release structure, or you can continue to handle them. We would have to run scikit-package on the directory to build those workflows and store them, but it shouldn't break anything. Just let us know.
vincefn commentedon Aug 26, 2026
I can continue to handle the libobjcryst releases. Hopefully we don't need them for much longer.
sbillinge commentedon Aug 26, 2026
closing as not needed atm per the comment above. No need to fix this as it should disappear with the nanobind migration.