Closed JCGoran closed 6 months ago
Logfiles from GitLab pipeline #195357 (:no_entry:) have been uploaded here!
Status and direct links:
Need https://github.com/BlueBrain/spack/pull/2320 to get merged, then the gitlab pipeline should be ✅ EDIT: Spack PR got merged, all green now :)
Logfiles from GitLab pipeline #195420 (:no_entry:) have been uploaded here!
Status and direct links:
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 88.40%. Comparing base (
bc913ef
) to head (8e7c5ca
).
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Logfiles from GitLab pipeline #195522 (:white_check_mark:) have been uploaded here!
Status and direct links:
Logfiles from GitLab pipeline #195710 (:white_check_mark:) have been uploaded here!
Status and direct links:
Logfiles from GitLab pipeline #195916 (:white_check_mark:) have been uploaded here!
Status and direct links:
Logfiles from GitLab pipeline #195934 (:white_check_mark:) have been uploaded here!
Status and direct links:
Logfiles from GitLab pipeline #195941 (:white_check_mark:) have been uploaded here!
Status and direct links:
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 87.17%. Comparing base (
2cff7e0
) to head (f8d41dd
).:exclamation: Current head f8d41dd differs from pull request most recent head 62b93f0. Consider uploading reports for the commit 62b93f0 to get more accurate results
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Minor annoyance: if we merge this, we need to add py-importlib-resources to the NMODL Spack recipe (only if we test on Python 3.8, if not, you can ignore this).
That doesn't seem wrong. The dependencies changed, hence the Spack recipe needs to change.
(Splitting this up from #1147 as it was getting too large).
As an example (stolen from one of the notebooks):
Running this with a freshly-installed wheel on latest master (built with
python setup.py bdist_wheel
) gives:Basically, due to the way loading of Python is handled, we should set the various env variables as soon as we load the module, otherwise the user may find mysterious errors.
Other changes:
importlib
)BREAKPOINT
statement to activate the sympy solver)NMODL_PYLIB
andNMODLHOME
env variables (only if they are not already set!)