Repository navigation
Conversation
39 of 61 tasks
The CI check jobs now run in the locked pixi environment (pixi.toml + committed pixi.lock), so make pixi the recommended way to create a development environment: - new 'Creating a development environment with pixi' section (install, pixi install/shell/run, the py314 environment, and the dependency-update policy: pixi.toml + Renovate-managed pixi.lock, exclude-newer cooldown) - note in the conda section that environment.yml now mirrors pixi.toml and is still used by readthedocs - generalize references to 'the conda environment' in the docs-building and installation-check pages
…ion workflow - pixi.lock was still ignored by .gitignore, so it never made it into the branch: setup-pixi (cache: true) fails with "Failed to generate cache key" on every check/check-py314 job, and the environments were not actually locked. Remove it from .gitignore and commit the generated lockfile. - the integration workflow quoted $MATRIX_ARGS, merging all KEY=VALUE pairs of matrix.ARGS into a single argument that integration_tests.py cannot split, breaking e.g. MYSQL_VER=mariadb:11.4.3 ES_VER=... (invalid docker reference) and the backward-compatibility job (mangled installation branch). Restore the word-splitting.
The plain $COMMAND expansion loses the single quotes around the pytest -k expression, so pytest tried to open 'test_BaseType_Unicode' as a file (ERROR: file or directory not found). Use eval, like the conda-based job did.
This was referenced Nov 17, 2026
fstagni
marked this pull request as ready for review
November 18, 2026 15:18
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part of DIRACGrid/.github#5 (adopt
pixieverywhere), stacked on #8891.The
checkandcheck-py314jobs ofbasic.ymldropsetup-miniconda+environment.ymlin favor of a locked pixi environment:pixi.toml: the dependency set mirrorsenvironment.yml(conda packages from thediracgrid+conda-forgechannels, plus the pip-only pieces: the DIRACGrid tornado forks and Authlib), with two environments:default(python 3.11) andpy314(python 3.14, replacing thesed-patched environment.yml workaround).pixi.lockis committed: the environments are reproducible, and Renovate (via the org preset) becomes the only path for dependency changes.exclude-newer = "7d"in the workspace config: per the org policy in chore: add the shared DIRACGrid Renovate config preset .github#7, the lock's release-age cooldown is enforced by the solver at lock time (Renovate's lockfile maintenance skipsminimumReleaseAge).dirac-common[testing],.[server,testing]) now run throughpixi run— behavior unchanged, dependencies come from the pixi environment.pylint-py27removal ([v9r0] chore: remove the pylint-py27 job #8894) removed the last conda-python-2.7 usage;deploy_CVMFSkeeps conda for the gsissh/CVMFS tooling (system-level, unrelated to the test environments).Verified locally:
pixi locksolves both environments withexclude-newerapplied. The rel-v9r0 and rel-v8r0 branches can adopt the same recipe once this is validated.