diff options
| author | Zeling Feng <zeling@google.com> | 2020-11-25 10:22:15 -0800 |
|---|---|---|
| committer | gVisor bot <gvisor-bot@google.com> | 2020-11-25 10:24:37 -0800 |
| commit | 4d59a5a62223b56927b37a00cd5a6dea577fe4c6 (patch) | |
| tree | ce210188d65e3cf94b10703087632933113dcdce /pkg/safecopy/memclr_amd64.s | |
| parent | d04144fbb7b9fcb055e3aa3c2246f9b498923cc0 (diff) | |
[3/3] Support isolated containers for parallel packetimpact tests
To create DUTs in parallel, we need to create goroutines to do the setup. The
old code base has a lot of t.Fatal(f) usage in those setup functions which is
not great for this change: "FailNow must be called from the goroutine running
the test or benchmark function, not from other goroutines created during the
test" (https://golang.org/pkg/testing/#T.FailNow).
- Cleanup all t.Fatal(f) usage in DUT.Prepare()
- use goroutines to create DUTs in parallel
PiperOrigin-RevId: 344275809
Diffstat (limited to 'pkg/safecopy/memclr_amd64.s')
0 files changed, 0 insertions, 0 deletions