# The acceptance entries, in gate order: : . The list of record (docs/plans/0040-release-pipeline.md # Entries mirrors its first two columns; deploy/check.sh compares them). staging: runs on a staging network only (it fills, restarts or installs # on the bidder hosts). Reclassifying an entry is the owner's decision. # seconds: what the entry took in the last full staging gate (hand cycle 4, 5ce234e4; 0020:run from cycle 3). Only a hint: tests/gate.sh # deals the entries into the shares of GATE_SHARD by it, longest first, so n networks end about together. A wrong number unbalances # the shares and nothing else (scripts/check-shards.sh proves every entry is in exactly one share for any number here). 0001:run both 932 0001:s2 staging 124 0002:run both 2402 0003:run both 75 0004:run both 319 0005:run both 584 0005:b both 461 0005:r2fail both 426 0006:run both 1 0006:compat both 99 0007:run both 65 0007:restart staging 96 0007:webrtc both 70 0007:upgrade staging 900 0007:fence staging 600 0007:ingress staging 600 0008:run both 145 0009:run both 88 0011:run both 0 0011:token both 2 0012:run both 87 0013:run both 239 0013:c both 546 0013:b staging 60 0014:run staging 147 0014:concurrent staging 308 0014:exhausted staging 128 0014:giveup staging 189 0014:wait staging 253 0014:impossible both 58 0014:abandon both 543 0014:backtoback staging 543 0014:overcommit staging 176 0014:memfit staging 178 0015:run both 82 0015:pressure staging 866 0016:run both 310 0016:badsha both 55 0016:bigmarker both 310 0017:run both 79 0017:killed both 126 0017:killedlate both 131 0017:half both 90 0017:devsup both 299 0017:samename both 36 0018:run staging 28 0019:run both 159 0020:run staging 200