| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| |
|
|
|
|
|
|
|
|
|
| |
By default dpkg-buildpackage signs the output if the d/changelog isn't
UNRELEASED.
If we ever change the d/changelog, we don't want it to fail because it
tries to sign things.
In the future, if and when we want to sign things, that probably won't
be done directly in gitlab CI when the package is built.
|
| |\
| |
| |
| |
| |
| |
| | |
Fix reproducible build CI job for macOS
Closes #1394 and #1507
See merge request tpo/core/arti!2377
|
| | |
| |
| |
| | |
See: tpo/core/arti#1394.
|
| |\ \
| | |
| | |
| | |
| | | |
Run tests of every crate, with all features disabled
See merge request tpo/core/arti!2350
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We can't do this for every crate.
I looked at what is now matrix-check to see if I wanted to use any of
the code. But it seems too entangled with its particular purpose, and
has a lot of embedded knowledge of our crates' features. I found it
sufficiently far from what I wanted that I decided on a fresh script.
|
| | | |
| | |
| | |
| | |
| | | |
There's a TODO asking for `check` to be changed to `test`. And we're
about to invent a thing that does, sort of, the `test`.
|
| | | |
| | |
| | |
| | | |
The rules: was removed from these jobs but this one was missed.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | |/
|/| |
|
| |/ |
|
| |
|
|
|
|
|
| |
My efforts to fix it by flailing with CC versions have not been
successful.
We need CI passing so we can continue to do other work.
|
| |
|
|
|
| |
(This is what we do in all the other CI tests when we want to
cargo-install something.)
|
| |
|
|
|
|
|
| |
With the introduction of FFI, we ship generated header files
that we need to keep up-to-date. This CI test double-checks
that the generated files match those that we would generate from
cbindgen.
|
| |
|
|
| |
This enables us to test "restricted discovery" mode in shadow.
|
| |
|
|
|
|
|
|
| |
Relative directory reference here is incorrect since we changed
directories. Move this line to before the directory-change.
Looks like this was broken in c4e1d0c582164e17e0226af754a08692da5efb29,
but only surfaces on a cache miss of the tgen build.
|
| |
|
|
|
|
|
|
| |
The -latest jobs don't actually have artifacts. But:
In the -latest jobs this can cause errors due to duplication: the
artifacts from the -recent jobs in the same pipeline result in EEXIST
errors.
|
| |
|
|
|
| |
This will let us make the artifact processing only happen when we want
to save artifacts.
|
| |
|
|
| |
Prompted by https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/2275#note_3054040
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
We replace uses of `amd64/rust:bookworm` in the `recent-*` jobs.
We add new latest-* jobs which
* aren't used for artifacts
* occur later in the pipeline
* only run on main, since we don't want them to block MRs
This is done with templates, to reuse the script parts.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Replace almost all the open-coded occurrences of `amd64/rust:bookworm`.
This rewinds us to Rust 1.79.
We can update after
https://github.com/rustsec/rustsec/issues/1217
is fixed upstream.
We're going to handle the rust-latest-* jobs specially.
There are still a few other images that look, from the name, like they
might be uncontrolled inputs into our CI, but they don't look risky.
Let's leave them for now.
|
| |
|
|
| |
So far only used by the cargo-audit job.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This avoids CI failures like this
https://gitlab.torproject.org/nickm/arti/-/jobs/617654
arising from situations like this
cargo-audit install fails with rust 1.80
https://github.com/rustsec/rustsec/issues/1217
error[E0282]: type annotations needed for Box<_>
https://github.com/time-rs/time/issues/693
IMO we should pin many of the other images too but I suspect that may
be controversial. I'm hoping that pinning this one to get CI working
is uncontroversial (perhaps only on a temporary basis).
The other way to solve this would be to remove --locked which IMO is
going in the wrong direction, by exposing us to more rather than fewer
uncontrolled inputs from our upstreams.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Without this, maint/shebang is broken.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
And delete our old version of the script.
|
| |
|
|
| |
We're about to switch to a version that doesn't support this.
|
| |
|
|
|
|
|
|
| |
* Change all in-tree reference
* Delete our copy of script, which now lives
in the rust-maint-common subtree.
* Leave a symlink behind, so that old git hooks that people
(IMO possibly unwisely) installed, still work.
|
| | |
|
| |
|
|
| |
What a palaver.
|
| | |
|
| |\
| |
| |
| |
| |
| |
| | |
CI: Split build-repro job
Closes #1478
See merge request tpo/core/arti!2252
|
| | |
| |
| |
| |
| | |
As suggested here:
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/2252#note_3046205
|
| | |
| |
| |
| |
| | |
This will allow the elements to run in parallel, hopefully speeding
things up (but using no fewer resources).
|
| | | |
|
| |/ |
|
| |
|
|
|
|
|
| |
Broken docs keep slipping in because we test this only with nightly,
where we allow failures.
Currently nightly is broken; see #1467. I'm not addressing that here yet.
|
| |
|
|
|
|
| |
Hopefully this will not be too slow.
Fixes #1472.
|
| |
|
|
| |
This reverts commit a6801c10584558316ff38f354167812d0c697549.
|
| |\
| |
| |
| |
| | |
Disable macos build tests
See merge request tpo/core/arti!2226
|
| | | |
|
| |/
|
|
|
| |
Ideally we'd tolerate situations with unaccepted ownership requests,
but that information doesn't seem to be public.
|