| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| |\
| |
| |
| |
| | |
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.)
|
| | |
| |
| |
| |
| | |
If the directories are absent, then deleting them gives you a line
in stderr, even if you do "rm -f foo || true".
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Now the shell is controlled by the presence of an -i flag, and can
be combined with a command.
This commit also adds usage messages and better reports for a couple
of kinds of setup errors.
|
| | |
| |
| |
| | |
Also improve comments and stdout slightly...
|
| |/ |
|
| | |
|
| |
|
|
|
| |
usage: with_coverage <command> [args...]: run <command> with [args...]
with_coverage : run bash
|
| |
|
|
|
|
|
| |
It formats them in a nice little json object, which it writes to
stdout.
Part of arti#172
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
We need this for clock_gettime_nsec_np().
The source is not canonical, but neither was the one we were using
before. To mitigate this, I've added a digest check on the SDK after
downloading it.
A 100% real canonical reproducible build process will probably
require Apple hardware anyway.
Closes #221
|
| |
|
|
|
|
| |
This doesn't actually do the right thing: it will make somebody get
ignored completely for a release if they _only_ use their
alternative name.
|
| | |
|
| | |
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Disclaimer: I have no idea what I'm doing when it comes to shell
scripts.
maint/thanks.sh autogenerates a list of contributors since a revision
(that you pass it on the command line), intended to make the work of
going through the shortlog a bit less manual. It can exclude
contributors' names given in maint/exclude_contributors.txt, in order to
filter out people who work for Tor, or who commit under more than one
name.
|
| |/ |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Also, tell the "typos" tool to ignore Cargo.lock.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Thanks to the chrono update, we no longer include an
obsolete/vulnerable version of the `time` crate. Unfortunately, it
turns out that chrono has the same trouble as `time`: it, too, looks
at the environment via localtime_r, and the environment isn't
threadsafe.
One step forward, one step back. At least the underlying issue is
one that lots of people seem to care about; let's hope they come up
with a solution.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
Previously I'd hoped to have it only apply to reproducible builds,
but the work of keeping it up-to-date and checking it for drift
seems to have been tripping us up. Let's try doing it the other way
for now, and we'll see how that goes.
|
| | |
|
| | |
|
| |
|
|
|
| |
Linux hash : c024778da162cda77869c46d162729d012a7758bee973bc83fa78c964d080903
Windows hash : e97e171740b889b7e3722b79c3763177174baac7fa34a5c3615c999298e1bc48
|
| |
|
|
|
| |
This will cause some pain for now, but now is really the best time
to do this kind of thing.
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
And convert some `add_or_port` calls to use `SocketAddr` instead of
parse + unwrap on strings.
> Note, this last change is only for IPv4 addresses, for now, and only
> within tests.
|
| | | |
|
| | |
| |
| |
| | |
sha256: 7f190568fa05f71ad356dc56a7a9725a4be18e5e40d6880f469e22981a18edd7
|
| | |
| |
| |
| |
| |
| | |
see https://github.com/rusqlite/rusqlite/issues/914
sha256: 684ebc4b8c270fc63beba185f6c54ceeb98734f13aa7aeca9b64acb33432a21c
|
| |/
|
|
|
| |
and make builds reproducible
sha256sum: f141c54929a43a31b9ed6b529f6f863aace87f7406818b2f8ffe2b7a5e2803fb
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
> Check `implicit_clone` section of Clippy documentation for details;
>
> https://rust-lang.github.io/rust-clippy/master/index.html#implicit_clone
This adds, and addresses, the following Clippy configuration to crates;
#![deny(clippy::implicit_clone)]
And moves related line within `maint/add_warning.py` file. My intent is to
mitigate extra edits after merging, so please let me know if I need to do this
last bit differently.
|
| | |
|
| | |
|
| | |
|