move the nightly env into its own file - #11481
Conversation
This avoids having to build binary dependencies on e.g. RTD in order to lock the dependencies.
github-actions
Bot
added
the
Automation
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
|
this appears to be ready now. The failing upstream-dev tests are also visible on Edit: not sure what to do about the Note that this depends on Parcels-code/pixi-lock#21, so we should merge only after that was merged and the references to my fork were removed (cc @VeckoTheGecko) |
|
this should be ready for reviews now (the nightly CI fails with the same errors on |
|
actually, I'll go ahead and merge this now. Any DX improvements (like creating a pixi task to run the nightly tests) can be separate PRs. As usual, if this breaks anything we can revert and I'll investigate afterwards. |
* move the nightly env into its own file This avoids having to build binary dependencies on e.g. RTD in order to lock the dependencies. * create the lockfile in a separate step * use the separate pixi file * let `pixi` infer the actual file * formatting * typo * demonstrate the use of the manifest path in `pixi-lock` * [skip-rtd][test-upstream] * next try * ignore the unreleased commit hash * [skip-rtd][test-upstream] * cache the nightly pixi.toml [skip-rtd] * back to explicitly specifying the path [skip-rtd][skip-ci] * correct the path of `xarray` * another new version of the action[skip-rtd][skip-ci] * pass the manifest path to the restore action[skip-rtd][skip-ci] * next version of the action[skip-ci][skip-rtd] * next attempt [skip-ci][skip-rtd] * bump the issue-from-pytest-log action * also get the mypy ci to run [skip-ci][skip-rtd] * back to a official version * upload the correct lock file as an artifact [skip-ci][skip-rtd]
2 participants
This avoids having to build binary dependencies on e.g. RTD in order to lock the dependencies.
This won't actually do anything besides accelerating the locking, until we change the upstream-dev ci. For that we need to have
parcels-code/pixi-locksupport themanifest-pathorworking-directoryoptions ofsetup-pixi(cc @VeckoTheGecko), and we also need to change the commands we use to run the tests. I may be able look into both this week.Ultimately we're working around two restrictions in
pixiwith this:For reference, I saw @TomNicholas did something very similar for
virtualizarra couple of months ago, except that is usingpipto modify the environment.