Test One-line Installation of Robotology MATLAB/Simulink Packages CI Failure End of August 2022

[traversaro]

No description provided.

[traversaro]

Most failures are:

  Looking for: ['yarp-matlab-bindings', 'idyntree-matlab-bindings', 'wb-toolbox', 'osqp-matlab', 'casadi-matlab-bindings', 'whole-body-controllers', 'matlab-whole-body-simulator', 'icub-models']
  
  
  Pinned packages:
    - python 3.10.*
  
  
  Encountered problems while solving:
    - package casadi-matlab-bindings-3.5.5.1-h9c3ff4c_10 requires casadi >=3.5.5,<3.6.0a0, but none of the providers can be installed
  
  Installation of robotology packages completed
  Creating setup script in /home/runner/work/robotology-superbuild/robotology-superbuild/scripts/robotology_setup.m
  Deleting mambaforge installer
  robotology MATLAB and Simulink packages are successfully installed!
  Please run /home/runner/work/robotology-superbuild/robotology-superbuild/scripts/robotology_setup.m before using the packages,
  or just add that script to your startup.m file, to run it whenever you open MATLAB.
  To uninstall these packages, just delete the folder /home/runner/work/robotology-superbuild/robotology-superbuild/scripts/robotology-matlab .

I think this is related to #1237 and conda-forge/miniforge#333 . The PR conda-forge/miniforge#333 switched the latest miniforge to include python 3.10, but as python 3.10 was not in the conda-forge pinned packages until few hours ago (see conda-forge/conda-forge-pinning-feedstock#3273), we do not have icub-main packages compatible with python 3.10 (see #1237).

Regenerating new conda packages after conda-forge/miniforge#333 should solve the problem.

[traversaro]

Regenerating new conda packages after conda-forge/miniforge#333 should solve the problem.

Indeed, this worked fine and now the CI is working fine.