• Dridi Boukelmoune's avatar
    Don't protect the barriers list with a lock · 2d927b12
    Dridi Boukelmoune authored
    A command like `barrier r1` would fail while holding the lock because of
    the invalid name, but the reset of the test case would then deadlock. It
    leads to a timeout like we see sometimes on VTEST so getting rid of them
    may just require to review when `vtc_fatal` is called while locking.
    
    In this very case we can only create barriers in the top thread so the
    lock is useless.
    2d927b12
Name
Last commit
Last update
..
tests Loading commit data...
tests.disabled Loading commit data...
Makefile.am Loading commit data...
Makefile.phk Loading commit data...
flint.lnt Loading commit data...
flint.sh Loading commit data...
hpack.h Loading commit data...
programs.h Loading commit data...
vmods.h Loading commit data...
vtc.c Loading commit data...
vtc.h Loading commit data...
vtc_barrier.c Loading commit data...
vtc_client.c Loading commit data...
vtc_h2_dectbl.h Loading commit data...
vtc_h2_enctbl.h Loading commit data...
vtc_h2_hpack.c Loading commit data...
vtc_h2_priv.h Loading commit data...
vtc_h2_stattbl.h Loading commit data...
vtc_h2_tbl.c Loading commit data...
vtc_http.c Loading commit data...
vtc_http.h Loading commit data...
vtc_http2.c Loading commit data...
vtc_log.c Loading commit data...
vtc_logexp.c Loading commit data...
vtc_main.c Loading commit data...
vtc_process.c Loading commit data...
vtc_proxy.c Loading commit data...
vtc_server.c Loading commit data...
vtc_subr.c Loading commit data...
vtc_varnish.c Loading commit data...
witness.py Loading commit data...