You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+22-17Lines changed: 22 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,9 +5,23 @@ This repo contains the testsuite that is used by both [Pixi] CI and [pixi-build-
5
5
6
6
## Local development
7
7
8
-
First make sure that you have both the [Pixi] and [pixi-build-backends] repositories checked out locally.
8
+
The tests can use the pre-built binaries produced by the Pixi and pixi-build-backends CI workflows. Download the latest artifacts for your platform:
9
9
10
-
Then, create a `.env` file at the repository root with the paths to your checked out repositories filled in.
10
+
```shell
11
+
pixi run download-artifacts
12
+
```
13
+
14
+
The binaries are stored in `artifacts/`, alongside a `download-metadata.json` file that records which branch or PR each artifact originated from. When running locally the script will reuse the active `gh auth` session; if `gh` is unavailable, set `GITHUB_TOKEN` or pass `--token`. Use `--repo pixi` or `--repo pixi-build-backends` to fetch artifacts for a single project.
15
+
16
+
With the artifacts in place you can run the fast subset of the tests (or any other Pixi task):
17
+
18
+
```shell
19
+
pixi run test
20
+
```
21
+
22
+
### Using local builds instead of artifacts
23
+
24
+
If you prefer to use local checkouts, create a `.env` file with the paths to your repositories:
0 commit comments