summaryrefslogtreecommitdiff
path: root/.gitlab-ci.yml
Commit message (Collapse)AuthorAgeFilesLines
* Enable the build-repro CI job in MR jobsIan Jackson2024-06-261-4/+1
| | | | | | Hopefully this will not be too slow. Fixes #1472.
* Revert "Disable macos build tests"Ian Jackson2024-06-261-1/+2
| | | | This reverts commit a6801c10584558316ff38f354167812d0c697549.
* Merge branch 'no-osxcross' into 'main'gabi-2502024-06-251-2/+1
|\ | | | | | | | | Disable macos build tests See merge request tpo/core/arti!2226
| * Disable macos build testsIan Jackson2024-06-251-2/+1
| |
* | Turn crate ownership discrepancies into a warningIan Jackson2024-06-241-0/+1
|/ | | | | Ideally we'd tolerate situations with unaccepted ownership requests, but that information doesn't seem to be public.
* Check crate ownership in CI, but only on mainIan Jackson2024-06-241-0/+13
| | | | | | | | | | | | | | | I think that the effect of this will be as follows: * MR branches will never run this, so when the crate ownership is wrong, development can continue. * When a new crate is first published, it will transition from "ignored" to "complaining". This will happen on the first CI run on main after "cargo publish" is run. But it *won't* happen on the CI run on the publication tag. The intent is that we discover a failure to `git add` while the release technician who published the new crate is still around.
* CI: Bail if unexpectedly using a non-amd64 containerJim Newsome2024-06-181-0/+20
| | | | | | | | cf https://gitlab.torproject.org/tpo/tpa/team/-/issues/41621, it's possible to unexpectedly run on a container for a different architecture than the one requested. This can result in subtle and difficult to debug issues, e.g. when unexpectedly running in the i386 variant of a container instead of the expected amd64 variant.
* CI: use single-arch docker images where availableJim Newsome2024-06-171-24/+47
| | | | | | | | Images with multi-arch manifests suffer from subtle caching issues that can result in running an image with a different arch than intended. See https://gitlab.torproject.org/tpo/tpa/team/-/issues/41621. We can avoid this issue by using single-arch manifests where available.
* shadow test: bump shadow version to 3.2Jim Newsome2024-06-081-1/+1
| | | | | This includes a fix for a (rare) panic-causing race condition, and misc other additions and improvements.
* mypy: Enable strict modeIan Jackson2024-05-281-1/+1
| | | | | | | Consultation with a nearby Python expert, on another topic, revealed that without --strict, mypy turns most of its stuff off by default. Sadly (?) this bureaucracy didn't find any bugs.
* Merge branch 'ci-after-script-tweaks' into 'main'Nick Mathewson2024-05-161-19/+6
|\ | | | | | | | | CI: Move cargo clean section to after_script. See merge request tpo/core/arti!2159
| * CI: Move cargo clean section to after_script.Nick Mathewson2024-05-151-19/+6
| | | | | | | | | | | | | | | | | | | | | | Part of arti#1410. The idea here is to consolidate `cargo clean` in an after_script section we call everywhere, rather than have it be in one that we can forget to copy. We can't call `cargo clean` unconditionally, though, since some of our jobs don't install cargo. So we make sure it's there.
* | Merge branch 'links' into 'main'Nick Mathewson2024-05-161-0/+15
|\ \ | | | | | | | | | | | | | | | | | | Provide and run script for making/checking link blocks in CHANGELOG.md Closes #1388 See merge request tpo/core/arti!2126
| * | CI: Run mypy on the (so far, 1) type-annotated Python3 fileIan Jackson2024-05-071-0/+7
| | |
| * | Run maint/update-md-links in CIIan Jackson2024-05-021-0/+8
| | |
* | | Forbid scripts names from specifying their implementation languageIan Jackson2024-05-161-0/+1
| | |
* | | Rename tests/shadow/run.sh to runIan Jackson2024-05-161-1/+1
| |/ |/|
* | Merge branch 'new_ci_cfg_strategy' into 'main'Nick Mathewson2024-05-071-6/+5
|\ \ | | | | | | | | | | | | | | | | | | add_warning/CI: New strategy to avoid "unexpected-cfgs" warning Closes #1395 See merge request tpo/core/arti!2129
| * | CI: Use new add_warning features in place of --cfg.Nick Mathewson2024-05-061-6/+5
| | |
* | | Merge branch 'chutney' into 'main'Nick Mathewson2024-05-061-1/+1
|\ \ \ | |/ / |/| | | | | | | | CI: disable chutney tests in coverage job too See merge request tpo/core/arti!2120
| * | CI: disable chutney tests in coverage job tooIan Jackson2024-04-301-1/+1
| |/ | | | | | | | | | | | | | | | | Followup to !1488. Apropos #1299. Ideally these would be replaced by shadow tests. At a future point, when they've not been used for ages, we could delete the chutney scripts etc.
* / CI: allow uexpected-cfgs when building docsNick Mathewson2024-05-061-1/+1
|/ | | | Without this, our rustdoc CI build will fail on nightly because of
* CI: Enable vanguards in the shadow tests.Gabriela Moldovan2024-04-051-1/+1
|
* downgrade alpine used for reproducible buildstrinity-1686a2024-03-291-1/+1
| | | | temporary fix for broken macos builds
* CI: Don't build arti with experimental features in rust-latest.Gabriela Moldovan2024-03-141-1/+2
| | | | | | | | Some experimental features (i.e. `vanguards`) break the shadow integration tests. Since the examples enable `experimental`, we need `rust-latest` to build arti using `-p arti`, rather than from the workspace level (because cargo does feature unification when building the packages as a workspace).
* arti, CI: Add a test case for command line helpIan Jackson2024-03-051-0/+6
|
* upgrade docker image for reproducible buildstrinity-1686a2024-03-031-1/+1
|
* shadow ci: stop pulling libigraph from bullseyeJim Newsome2024-02-051-19/+2
| | | | | Now that https://github.com/shadow/tgen/issues/44 is fixed, we no longer need to do this.
* shadow ci: bump to latest tgen releaseJim Newsome2024-02-051-1/+1
|
* shadow ci: bump to latest shadow releaseJim Newsome2024-02-051-3/+1
|
* Merge branch 'ci3' into 'main'Nick Mathewson2024-01-311-0/+2
|\ | | | | | | | | CI: Run coverage test on bigger runners See merge request tpo/core/arti!1944
| * CI: Run coverage test on bigger runnersIan Jackson2024-01-311-0/+2
| | | | | | | | | | | | | | | | | | | | | | This is starting to get SIGKILL during linking. Lack of memory, presumably. @anarcat suggests we should run this on bigger runners, and that this could be achieved by applying the `tpa` tag. CC @trinity-1686a See also !1943.
* | Merge branch 'ci' into 'main'gabi-2502024-01-311-0/+2
|\ \ | | | | | | | | | | | | CI: Run some tests a bit earlier See merge request tpo/core/arti!1940
| * | CI: blocking-todos: Run quicklyIan Jackson2024-01-311-0/+1
| | | | | | | | | | | | | | | This is a very fast check. It's last in the list so that nothing gets blocked *by* it, but we want it to run early.
| * | CI: minimal-versions: Block only on rust-checksIan Jackson2024-01-311-0/+1
| |/ | | | | | | | | In particular, let's not wait for all the other builds, to make iterating minimal-versions through CI less painful.
* / CI: Run coverage test only in scheduled pipelinesIan Jackson2024-01-311-0/+2
|/ | | | | | | | This is starting to get SIGKILL during linking. Lack of memory, presumably. @nickm suggests running it only daily since apparently we don't look at the output that often anyway.
* arti-extra build: enable onion-service-serviceJim Newsome2023-12-131-1/+1
|
* arti-extra build: no-op reformatJim Newsome2023-12-131-1/+5
|
* Enable ntor_v3 in the arti-extra buildJim Newsome2023-12-071-1/+1
| | | | This tests ntor_v3 in the shadow integration test.
* Merge branch 'msrv-bump-1.70' into 'main'Ian Jackson2023-11-301-3/+1
|\ | | | | | | | | Increase our MSRV to 1.70 See merge request tpo/core/arti!1773
| * CI: change minimal-versions to 1.70.Nick Mathewson2023-11-281-3/+1
| |
* | Fix extra features getting enabled in the arti-extra test binaryJim Newsome2023-11-281-1/+5
|/ | | | | | | We were missing `-p arti` in the build command. As a result we were getting the union of all features requested by anything in the workspace, including an example enabling the `experimental` feature which enables a bunch of other things.
* use ipv6 runner instead of tpa for coveragetrinity-1686a2023-11-221-1/+1
|
* add tpa tag to coverage-aggregatedtrinity-1686a2023-11-161-0/+2
| | | | otherwis it fails when it gets scheduled on a non-ipv6 ready runner
* update rustc for reproducible buildstrinity-1686a2023-11-161-1/+1
|
* remove artifact generation from rust-latest-test-all-featurestrinity-1686a2023-10-131-5/+0
|
* move usage of ./maint/preserve out of after_scripttrinity-1686a2023-10-131-3/+3
|
* CI: Remove amd64 tagsIan Jackson2023-09-181-18/+0
| | | | | | | | | | | | | | | We have a new runner, and apparently to use it better we want to remove these tags. TBH this seems rather unprincipled. In theory, shouldn't we tag with `amd64` all the jobs that we definitely want to run on that arch, and the others can run on whatever is the default? Then in the glorious distant RISCV future everything will run on riscv64 by default? But maybe we wouldn't want to switch that as part of the infrastructure anyway? Anyway, for discussion see https://gitlab.torproject.org/tpo/tpa/team/-/issues/41295#note_2943129
* CI: Ensure libssl3 is installed in shadow and chutney testsJim Newsome2023-09-051-4/+4
|
* CI: Ensure libsqlite3 is installed in shadow and chutney testsJim Newsome2023-09-051-0/+5
|
generated by cgit v1.2.3 (git 2.46.0) at 2026-08-26 18:46:07 +0000