| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| |
|
|
|
|
|
|
|
| |
The new version of derive_builder requires a newer darling.
Ooops. Upstream MR here:
https://github.com/colin-kiegel/rust-derive-builder/pull/242
For now, upgrade darling. When there's a new upstream derive_builder,
we can use it and drop this.
|
| |
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
|
| |
fix #378
also fix unrelated error in nightly rustdoc CI
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
| |
See !352
|
| | |
|
| |
|
|
|
|
|
|
| |
The *earlier* versions of these crates pull in *dependencies* that
violate our MSRV policy by requiring a *later* version of Rust.
Empirically, env_logger 0.5.4 would be enough, but practice here seems
to be to just say "cargo update".
|
| |\
| |
| |
| |
| | |
Upgrade a few dependencies to newer versions
See merge request tpo/core/arti!357
|
| | | |
|
| | | |
|
| | | |
|
| |/ |
|
| | |
|
| |
|
|
| |
This is a program, with a main function, etc.
|
| |
|
|
|
|
| |
Update all references. There are three remaining hits for
git-grep '\.py\b'
all of which are scripts in "little-t-tor", not here in arti.
|
| |
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
| |
Closes #338.
|
| | |
|
| | |
|
| |\
| |
| |
| |
| | |
add postprocessing script to deduplicate cobertura reports
See merge request tpo/core/arti!272
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| |/ |
|
| |
|
|
|
|
|
|
| |
Shellcheck doesn't like it when you do `rm -r "$A/$B"` : it worries
that the path might accidentally expand to /.
That shouldn't actually be possible in this case, but let's avoid
being the people who accidentally remove somebody's filesystem.
|
| |
|
|
|
| |
This was added in !210; looks like it got removed by mistake with
!221.
|
| |
|
|
|
| |
This makes it easier to see when they're changing, and will make
future patches easier to review.
|
| |\
| |
| |
| |
| |
| |
| | |
Add test coverage tracking with CI/CD
Closes #250
See merge request tpo/core/arti!221
|
| | |
| |
| |
| | |
Follows up on changes from https://gitlab.torproject.org/trinity-1686a/arti/-/merge_requests/2/diffs#bc2cc73a8917fa6fed183148df69119665eb4e55
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
There's some kind of bug in nightly that (for me) keeps grcov from
generating correct results. Instead, it misses some crates entirely.
No trouble, though: I can just use an older nightly until they get
this issue fixed!
This patch makes using a different version of nightly possible with
a new RUST_COVERAGE_TOOLCHAIN environment variable.
|
| | |
| |
| |
| | |
found by shellcheck.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
`coverage.sh` is now a more elaborate script to before, thanks to
moving from tarpaulin to grcov via `with_coverage.sh`.
This commit also adds support for the minimalistic
chutney+curl-based integration test from our gitlab-ci.yml file.
See the message from "coverage.sh -h" for information about running
these tests.
Closes #248.
|
| | | |
|
| | |
| |
| |
| |
| | |
(We don't put Tor Project employees in the acknowledgments lists.
And we probably shouldn't put bots either.)
|
| |/
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
|
| |
This program is itself for testing; we don't strongly care how much
coverage it has on its own.
|
| |
|
|
|
| |
Fix a bug in postprocess_coverage.py that stuck a big row of '
characters in its output.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This change jettisons the awk and ed dependencies and instead uses a
real HTML parser, via the BeautifulSoup library in python.
Using BeautifulSoup lets us do trickier stuff, like actually
extracting the coverage totals and adding our own table, with
per-crate coverage.
The script only does this post-processing when it finds python3; the
script exits with an error if BeautifulSoup isn't installed.
|
| | |
|
| |\
| |
| |
| |
| | |
UX improvements to with_coverage script
See merge request tpo/core/arti!143
|
| | |
| |
| |
| | |
The syntax is kinda minimal, but it seems to work okay.
|
| | |
| |
| |
| | |
Applies a suggestion from @trinity-1686a
|
| | |
| |
| |
| |
| | |
This is a slight kludge, but it helps a lot to keep track of what
exactly was tested for coverage.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
If the -c flag is provided, we _continue_ with the previous
consensus_meta data (without deleting it).
If the -s flag is provided, we _skip_ generating the final report
(since we're going to be doing more profiling.)
|