| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
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.
|
| |\
| |
| |
| |
| | |
CI: Move cargo clean section to after_script.
See merge request tpo/core/arti!2159
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Provide and run script for making/checking link blocks in CHANGELOG.md
Closes #1388
See merge request tpo/core/arti!2126
|
| | | | |
|
| | | | |
|
| | | | |
|
| | |/
|/| |
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
add_warning/CI: New strategy to avoid "unexpected-cfgs" warning
Closes #1395
See merge request tpo/core/arti!2129
|
| | | | |
|
| |\ \ \
| |/ /
|/| |
| | |
| | | |
CI: disable chutney tests in coverage job too
See merge request tpo/core/arti!2120
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| |/
|
|
| |
Without this, our rustdoc CI build will fail on nightly because of
|
| | |
|
| |
|
|
| |
temporary fix for broken macos builds
|
| |
|
|
|
|
|
|
| |
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).
|
| | |
|
| | |
|
| |
|
|
|
| |
Now that https://github.com/shadow/tgen/issues/44 is fixed, we no longer
need to do this.
|
| | |
|
| | |
|
| |\
| |
| |
| |
| | |
CI: Run coverage test on bigger runners
See merge request tpo/core/arti!1944
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| |\ \
| | |
| | |
| | |
| | | |
CI: Run some tests a bit earlier
See merge request tpo/core/arti!1940
|
| | | |
| | |
| | |
| | |
| | | |
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.
|
| | |/
| |
| |
| |
| | |
In particular, let's not wait for all the other builds, to make
iterating minimal-versions through CI less painful.
|
| |/
|
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| |
|
|
| |
This tests ntor_v3 in the shadow integration test.
|
| |\
| |
| |
| |
| | |
Increase our MSRV to 1.70
See merge request tpo/core/arti!1773
|
| | | |
|
| |/
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
| |
otherwis it fails when it gets scheduled on a non-ipv6 ready runner
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Workaround for https://github.com/shadow/tgen/issues/44
|
| |
|
|
|
|
|
|
| |
Thesee jobs are ones which don't interact with our Rust executables.
Since `debian:stable-slim` has already been updated I believe, I think
this actually makes no difference right now. But it will prevent us
unexpectedly picking up Debian updates.
|
| |
|
|
|
| |
`rust:latest` updates to a new Debian willy-nilly, which broke our CI
due to it being an uncontrolled dependency.
|
| |
|
|
|
|
| |
This avoids us trying to run binaries built on one image, on a
different one. I believe that this is supposed to work according to
Rust doctrine, but empirically it doesn't.
|
| |
|
|
|
| |
Debian's pip3 now apparently complains when root is running it,
which breaks our old coverage CI.
|
| |
|
|
|
|
|
| |
This was added in 9357a8fd6b22 "ci: add shebang to the GitLab CI" as
part of !990 to the `maint-checks` job; but the actual additional
check was added to the `doc-features` job (by mistake, fixed in
!1490); and, that shebang check script doesn't need git anyway.
|
| |
|
|
|
|
|
| |
Currently, the shebang check CI is not executed, as it would need to
fail then.
See !1489
|
| | |
|