Updating ciceroscmpy version and tests this also gets rid of pandas <…

[maritsandstad]

…2 requirement

[maritsandstad]

Should I try to up the test coverage for my various help functions in this while I'm at it @znicholls ?

(Otherwise this might just be a quick update version thing just to get less outdated versioning...)

[codecov]

Codecov Report

Attention: 1 lines in your changes are missing coverage. Please review.

Comparison is base (b3c8cbf) 70.38% compared to head (2c73e06) 70.38%.
Report is 1 commits behind head on master.

Files	Patch %	Lines
...dapters/utils/cicero_utils/make_scenario_common.py	0.00%	1 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##           master      #89   +/-   ##
=======================================
  Coverage   70.38%   70.38%           
=======================================
  Files          36       36           
  Lines        1442     1442           
  Branches      194      194           
=======================================
  Hits         1015     1015           
  Misses        405      405           
  Partials       22       22           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[znicholls]

Should I try to up the test coverage for my various help functions in this while I'm at it @znicholls ?

If you want, can also be done in a follow up PR to keep the scope of each smaller

[maritsandstad]

Seems I need to spend some time fighting with windows first, anyways...

[znicholls]

Seems I need to spend some time fighting with windows first, anyways...

The error is really bizarre. The CI shows the environment at the top in case that's helpful (maybe different package versions available on windows compared to linux...)

e.g. CI https://github.com/openscm/openscm-runner/actions/runs/7708984548/job/21009201207?pr=89

If you scroll to the right bit you see

[maritsandstad]

Ok, fixed the windows thing, apparently windows default int type for numpy is np.int32... Anyways, the fail now is coverage, so if the tests are supposed to go green, then I might need to work on that...

[znicholls]

Don't worry about the coverage, that's just coverage being silly (I'll just override it when I merge).

If you can mark the PR as ready for review and make the updates then I'll merge assuming everything goes green (once it's no longer a draft, a couple more things get run which may flag further errors).

[maritsandstad]

Ok, think that covers the rest of the updates :-)