| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| |
|
|
|
|
|
|
|
| |
Formerly, the "launch a chutney network" code was duplicated in
"setup" and "arti-bench", since "setup" always launched an arti
proxy, while "arti-bench" didn't want that functionality.
Now the "setup" script launches an arti proxy conditionally,
depending on whether the "proxy" argument is given.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
The Rust upgrade is necessary since our Cargo.lock file now requires
`ed25519` 1.4.0, which requires edition2021, which requires Rust
1.56 or later.
The Alpine upgrade is opportunistic: we might as well.
I've also added comments to remind us to keep the .gitlab-ci.yml
and docker_reproducible_build files in sync, since my first version
of this commit messed that up.
Closes #376.
|
| |
|
|
|
|
|
|
|
| |
Move rust-nightly to stage test so it runs in parallel with coverage,
which are the two longest jobs, and currently run in sequence.
Don't document dependancies, should make the step about 50% faster
Use about 12M of cache to not recompile grcov each time
Don't compile grcov with coverage, we don't need it, it's probably
slower both to compile and execute
|
| |
|
|
|
|
|
|
|
| |
As per #309
Update all references. There is one remaining hit for
git-grep '\.sh\b'
namely "build.sh" in maint/reproducible_build, which I think is
the build script for osxcross - ie, an external project.
|
| |
|
|
| |
Right now it's failing on nightly through no fault of our own.
|
| |\
| |
| |
| |
| | |
arti-bench: run the benchmarks in CI, and keep the results
See merge request tpo/core/arti!283
|
| | |
| |
| |
| |
| | |
This adds `arti-bench` to the `integration` job in the CI pipelines, and
keeps around the JSON benchmark output for later comparison.
|
| |/ |
|
| |\
| |
| |
| |
| | |
Add editorconfig to force some rules (Final Newline)
See merge request tpo/core/arti!289
|
| | | |
|
| |/ |
|
| |\
| |
| |
| |
| | |
CI: Add "rustup show" to show compiler versions in logs
See merge request tpo/core/arti!276
|
| | |
| |
| |
| |
| |
| | |
Trying to debug the nightly failure here
https://gitlab.torproject.org/Diziet/arti/-/pipelines/25417
and I can't seem to repro it.
|
| |\ \
| |/
|/|
| |
| | |
add postprocessing script to deduplicate cobertura reports
See merge request tpo/core/arti!272
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| |/ |
|
| | |
|
| |\
| |
| |
| |
| |
| |
| | |
Refactor the tor-rtcompat API.
Closes #301 and #300
See merge request tpo/core/arti!263
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Previously it didn't enable any TLS provider, since we made
native-tls optional a few commits ago. Now it enables rustls,
so that rustls also gets a quick check along with async-std.
I've also switched this test to use "cargo clippy" in place of
"cargo test" because it's a strict superset.
|
| |\ \
| |/
|/|
| |
| |
| |
| | |
Add test coverage tracking with CI/CD
Closes #250
See merge request tpo/core/arti!221
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
Following suggestion here:
`https://gitlab.torproject.org/tpo/core/arti/-/issues/250#note_2764010`
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
Following instructions at:
`https://www.collabora.com/news-and-blog/blog/2021/03/24/rust-integrating-llvm-source-base-code-coverage-with-gitlab/`
|
| |/
|
|
|
|
|
|
|
|
| |
Previously this code was in .gitlab-ci.yml, but for the purposes of
testing my fix for #275, it turned out to be much better to have it
in a script of its own.
Also, we now need to update our "quote" second-order dependency,
since otherwise our minimal first-order dependencies won't build
correctly.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Because of arti#257, compatibility with earlier versions of rust are
broken: we hope this is temporary, but fixing it will probably
require a new version of rusqlite.
|
| |
|
|
|
|
|
| |
testing was done on a different target than building, so everything was
compiled twice (actually, it's the same target, but rust doesn't realize
that)
makes build+test about 20% faster
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch makes the rust-nightly CI task fail if it detects any
dbg!(), println!(), or eprintln!() calls in production code.
Because of clippy limitations, it may also gripe about calls to
these macros in our tests. The preferred workarounds are to either
instead. Both are acceptable.
We're doing this check in CI rather than unconditionally with clippy
directives, since we often want to have these calls in our code
temporarily while we're developing. Some day we might want this
test to go into a pre-push hook.
This patch also adds #![allow()] directives for println!() and
eprintln!() in the arti crate. Since that one isn't a library, it's
okay for it to speak to stdout/stderr.
Closes #218.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This switches out `arti`'s argument-parsing library with `clap`, which
is a lot more featureful (and very widely used within the Rust
ecosystem). We also now use a lot of `clap`'s features to improve the
CLI experience:
- The CLI now expects a subcommand (currently, either "help", or "proxy"
for the existing SOCKS proxy behaviour). This should let us add
additional non-SOCKS-proxy features to arti in future.
- `clap` supports default values determined at runtime, so the way the
default config file is loaded was changed: now, we determine the
OS-specific path for said file before invoking `clap`, so the help
command can show it properly.
- The behaviour of `tor_config` was also changed; now, one simply
specifies a list of configuration files to load, together with
whether they're required.
- That function also way overused generics; this has been fixed.
- Instead of using the ARTI_LOG environment variable to configure
logging, one now uses the `-l, --log-level` CLI option.
(The intent is for this option to be more discoverable by users.)
- The `proxy` subcommand allows the user to override the SOCKS port used
on the CLI without editing the config file.
|
| |
|
|
|
|
| |
Solves a name conflict with the existing tor_client create.
Closes #130.
|