| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
|
|
|
| |
config
* build shadowtools python package in `build-shadow` job
* install the shadowtools python package in python3-checks, so that
usage can be checked with mypy.
* integration-e2e-shadow: generate typed shadow config
|
| |
|
|
|
| |
This keeps everything together and avoids clobbering previous artifacts,
since chutney already creates a unique nodes dir in every run.
|
| |
|
|
|
|
| |
This makes the chutney network configuration available *before* we
generate the shadow config file, which we need in order to generate
multi-host networks.
|
| |
|
|
|
|
| |
This is in preparation to move the init step outside of the shadow
simulation in integration-e2e-shadow (while leaving the bootstrap step
inside the shadow simulation).
|
| |
|
|
|
|
|
| |
This is in preparation to diverge somewhat. In particular, we want to do
some of the configuration and setup from *outside* of shadow, so that
we can generate shadow configs that take the chutney network
configuration into account.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
shadow's default behavior of spin-looping is bad behavior in a shared
environment.
This is already disabled in integration-shadow.
|
| |
|
|
|
|
| |
In CI, shadow's default behavior of pinning to CPU cores can result in
multiple instances of shadow fighting over the same CPU cores instead of
using idle ones.
|
| | |
|
| |
|
|
|
| |
No particular need to separate them, and the merged version is easier to
follow.
|
| | |
|
| |
|
|
|
|
| |
This wasn't a pre-existing environment variable, and now it can be set
via command-line if it needs to be overridden. I don't see much reason
to use an environment variable here.
|
| |
|
|
|
|
|
|
| |
In particular, this is to avoid floods of:
> compute_drain_rate(): Bug: Computing stream drain rate with zero time delta
in tor logs.
|
| |
|
|
|
|
| |
Since this significantly affects the behavior of the simulation, it's
probably worth having it in the yaml. (It can of course still be
overridden from the command-line).
|
| |
|
|
|
|
| |
Since this significantly affects the behavior of the simulation, it's
useful to have it in the yaml for reference or if the simulation is
manually rerun from the yaml.
|
| |
|
|
|
|
|
|
| |
This should make the simulation results generally more stable with
respect to small perturbations, such as adding logging.
It also causes a previous "heisenbug" failure in this test to reliably
reproduce in every run.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
Previously shadow would report a platform of "shadowsys" in the uname
syscall, which would cause chutney to disable sandboxing by default.
As of https://github.com/shadow/shadow/pull/3442, shadow now returns
"Linux", which causes the chutney default to enable sandboxing.
When sandboxing is enabled, the tor processes abort with error, since
shadow doesn't support the seccomp syscall.
|
| | |
|
| |
|
|
|
|
| |
We no longer need a path to a checkout of the chutney repository; we
just need the chutney binary itself. We still allow this to be set
explicitly with CHUTNEY_BIN, but fall back to finding it on the PATH.
|
| |
|
|
|
|
| |
The `black` formatter did most line wrapping for us, and we accept
its default of 88 characters there, but for comments and docstrings
(which black doesn't wrap) we allow up to 99 characters.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
"Black" is an "opinionated" python formatter, whose opinionatedness
is somewhat in the spirit of rustfmt.
This MR runs black with default settings on all of our python code
in Arti. It was produced by the following commands
```
# Everything in python/
black python/
# Everything with a .py extension
fd '.py$' -X black
# Everything with a python shebang.
git grep -l '#! */usr/bin/env *python' | xargs black
```
|
|
|
This is a wrapper script for running `tests/chutney/integration-e2e`
under shadow.
|
