| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
| |
Currently just copy-paste from the integration-chutney-shadow job.
This will be simplified and/or folded into an external script pending
<https://gitlab.torproject.org/tpo/core/chutney/-/merge_requests/31>.
Note that this job is currently disabled, making this commit roughly a
no-op. This is just to proactively try to keep this version of the job
unbroken for if and when we reenable it.
|
| |
|
|
|
| |
Since chutney is currently under relatively rapid development, let's
avoid surprise breakage in arti's CI.
|
| |\
| |
| |
| |
| |
| |
| | |
CI: Apply flake8, mypy, and black to all of our Python
Closes #1689
See merge request tpo/core/arti!2584
|
| | | |
|
| | |
| |
| |
| | |
Set "1 week" since I see that it's used on another shadow artifact.
|
| | | |
|
| | | |
|
| |/
|
|
|
| |
The changes in https://github.com/shadow/shadow/pull/3428 should add
more details to the CI output of Shadow simulations.
|
| |
|
|
| |
Mark it no longer experimental, but part of full. And document it.
|
| |
|
|
|
|
|
| |
As suggested
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/2561#note_3097441
I don't think we can have += since it may not be bash.
|
| |
|
|
|
| |
Work around awkward cargo behaviour and allow us to more reliably test
disabled features, even if they're enabled by default at lower levels.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This new feature lets us provide the "enable these options which are
needed to make the tests pass" featrure, which is different for each
of the afflicted crates. Then we can test these crates
tor-hsservice
arti
arti-client
which minimal features.
This will be important in a moment, as we're going to want to be
relying on actually minimal features tests in arti cfg.rs.
|
| | |
|
| |
|
|
| |
This detected the account lifetime bugs fixed in this branch.
|
| |\
| |
| |
| |
| |
| |
| | |
Use clippy to prevent non-mq use of mpsc::channel
Closes #1659
See merge request tpo/core/arti!2536
|
| | | |
|
| |/
|
|
|
|
|
| |
"python" meaning "python3" was a wrongheaded decision by Python
upstream. Our python scripts should start (roughly) `#! env python3`.
And, this is already the case - we don't actually use python-is-python3!
|
| |\
| |
| |
| |
| | |
shadow CI: Add a couple of tests involving C Tor keystores
See merge request tpo/core/arti!2514
|
| | |
| |
| |
| | |
This is needed to test C Tor keystore support in shadow.
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
There's no unsafe in this crate, but it does have some exciting drop
bomb stuff.
|
| | | |
|
| |/ |
|
| | |
|
| |
|
|
|
|
| |
I'm about to add some unsafe which I want tested in CI.
We must disable two tests.
|
| | |
|
| |
|
|
| |
This will allow us to upgrade to the latest version of rusqlite.
|
| | |
|
| | |
|
| |
|
|
|
| |
We'll want this in the shadow-chutney test too.
No harm in just doing it for all jobs.
|
| |
|
|
|
|
|
|
|
|
|
| |
Previously `tests/chutney/setup` would locate *or install* chutney and
set `CHUTNEY_PATH` for itself. However that `CHUTNEY_PATH` wasn't
propagated to other steps or "up" to the new `integration-e2e` wrapper
script.
Tracking it in the arti.run along with other dynamic info lets us ensure
we consistently use the same chutney across steps, and in the higher
level `integration-e2e` script.
|
| |
|
|
|
|
|
| |
Having this in a script is a step towards being able to run exactly the
same test under shadow without duplicating this high-level logic.
It's also convenient for running the ci test locally.
|
| | |
|
| |
|
|
|
|
|
| |
The effect of this is just to make the job run sooner. But it's
actually quite unlikely to fail, and nothing now depends on it, so we
should run it later along with the rest of the jobs in the `test`
stage.
|
| |
|
|
|
| |
This avoids any inherited data (eg from previous jobs) influencing the
output.
|
| |
|
|
|
|
|
|
|
| |
* Pass -b to dpkg-buildpackage, meaning "build binaries only".
* Don't `need` the source package job
* Don't try to import source package artifacts
This means we're not building the .debs from the .dsc, but we weren't
doing that anyway. (.dscs are IMPO obsolete...)
|
| |
|
|
|
|
|
|
|
|
|
| |
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.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | |/
|/| |
|
| |/ |
|
