New Release - Bob - 6.0.0
Nightlies are green;
https://gitlab.idiap.ch/bob/bob.nightlies/pipelines
Shall we consider a new release?
Activity
-
Newest first Oldest first
-
Show all activity Show comments only Show history only
- Owner
I'm ok.
It would be a good idea to fix/merge some stuff first:
- docs#6 (closed)
- docs#7 (closed)
- docs!10 (merged)
- #254 (closed) (Amir)
- https://gitlab.idiap.ch/bob/bob.conda/issues/61 (Amir) (Should be closed/tested after Bob release)
- Green nightlies https://gitlab.idiap.ch/bob/bob.nightlies
Edited by Tiago de Freitas Pereira - Owner
we are blocked by docs#7 (closed) as well.
- Author Owner
Hi @bob,
So many things changed in our base software stack and we can't release new software anymore. WE NEED A NEW
bob
RELEASE.I just updated the list of tasks that need to be done in order to start a new release.
Anyone willing to help ?
Thanks
- Owner
I can help fix #254 (closed) and https://gitlab.idiap.ch/bob/bob.conda/issues/61
- Author Owner
We are almost there with the green nightlies
https://gitlab.idiap.ch/bob/bob.nightlies/pipelines/30035
Only the Mac builds are failing
- Owner
The mac problem is related to missing settings on the test section of the bob/bob package.
To fix this, you'll need to set
export CONDA_BUILD_SYSROOT={{ CONDA_BUILD_SYSROOT }} # [osx]
as is done on bob/bob.extension. This should solve the issues. - Author Owner
Didn't work :-(
- Author Owner
Any insights for this one? https://gitlab.idiap.ch/bob/bob/-/jobs/164736
Shall I explicitly do
export MACOSX_DEPLOYMENT_TARGET=10.9 # [osx]
in themeta.yaml
?Thanks
- Owner
Try replacing the setting for CONDA_BUILD_SYSROOT with
MACOSX_DEPLOYMENT_TARGET={{ MACOSX_DEPLOYMENT_TARGET }}
. See if that works any better. Try locally first.@amohammadi: do you understand why that is correctly set for bob/bob.extension tests, but not for bob/bob tests?
- Owner
These tests are skipped in bob.extension because of circular dependency on bob.blitz
- Owner
Ah, OK. That makes sense and I now also remember that the
conda_build_config.yaml
variables are not set during test time. So, we will have to copy them during the build. Just include 3 lines on the test:- export SDKROOT={{ SDKROOT }} # [osx] - export CONDA_BUILD_SYSROOT={{ CONDA_BUILD_SYSROOT }} # [osx] - export MACOSX_DEPLOYMENT_TARGET={{ MACOSX_DEPLOYMENT_TARGET }} # [osx]
That should fix the test.
- Owner
Maybe you quote what comes after the
=
sign:- export SDKROOT="{{ SDKROOT }}" # [osx] - export CONDA_BUILD_SYSROOT="{{ CONDA_BUILD_SYSROOT }}" # [osx] - export MACOSX_DEPLOYMENT_TARGET="{{ MACOSX_DEPLOYMENT_TARGET }}" # [osx]
Looks wiser.
- Author Owner
I will do as we do with
bob.extension
and exclude thetests.extension
https://gitlab.idiap.ch/bob/bob.extension/blob/master/conda/meta.yaml#L44
- Owner
Please don't do that @tiago.pereira . We cannot run these tests in bob.extension and if we don't test them here, things which are important are going to break without us knowing.
Edited by Amir MOHAMMADI - Author Owner
Ok, do you have any idea on how to fix this without disabling the test cases?
thanks
- Owner
Can you reproduce this problem locally - should be easy just to run one test at your machine.
- Author Owner
I can reproduce it. I will try to isolate the problem.
- Tiago de Freitas Pereira mentioned in merge request bob.devtools!57 (merged)
mentioned in merge request bob.devtools!57 (merged)
- Author Owner
Still with issues. For some reason the environment variables are not exported as it was supposed to be with bob.devtools@7aee680b
Edited by Tiago de Freitas Pereira - Author Owner
Still f****d https://gitlab.idiap.ch/bob/bob.nightlies/-/jobs/165132/raw
I know we can set these variables via .bobrc Is there a way to set a .bobrc via ci?