1. 05 Sep, 2018 10 commits
  2. 04 Sep, 2018 13 commits
  3. 03 Sep, 2018 8 commits
  4. 31 Aug, 2018 1 commit
  5. 30 Aug, 2018 4 commits
    • Nils Goroll's avatar
      check if this stabilizes the test · cf04d394
      Nils Goroll authored
      cf04d394
    • Nils Goroll's avatar
      varnishtest: add -keepalive to repeat on a single connection · bfe1bcd8
      Nils Goroll authored
      For tests which do not require new connections for repetitions (for
      example because of possible error conditions), this reduces run time
      and the number of required ephemeral ports.
      
      The latter is a real issue when running many vtcs in parallel which
      each run many repetitions of the same test (for example to check for
      possible race conditions). When ephemeral ports are exhausted,
      seemingly unrelated issues like the following can be observed:
      
      ---- c1010 14.0 Failed to open 127.0.0.1 59763: (null)
      
      **** v1    1.8 vsl|          0 CLI             - Wr 300 65 Listen failed
      on socket '127.0.0.1:33328': Address already in use
      **** v1    1.8 vsl|          0 CLI             - EOF on CLI connection,
      worker stops
      
      An argument could be made that UDS does not suffer from the port
      exhaustion issue and thus such tests could be migrated to UDS. Yet
      also for this case the run time point remains, plus deliberately
      testing many iterations on a single connection could have its own
      merits.
      bfe1bcd8
    • Nils Goroll's avatar
    • Poul-Henning Kamp's avatar
      20ab2abc
  6. 29 Aug, 2018 3 commits
    • Nils Goroll's avatar
    • Nils Goroll's avatar
      initialize PRIV_TASK and PRIV_TOP vmod arguments once per subroutine · f03948f4
      Nils Goroll authored
      ... and fail the VCL unless successful.
      
      Providing the PRIVs to vmods is a core function, so error handling
      should happen outside vmods.
      
      Besides being safe, this initialization can be more efficient than
      previous code for PRIVs used frequently within the same subroutine.
      
      An alternative approach would be to initialize all privs once per
      task / top request, but unless all privs are actually used in a VCL,
      this approach could impose significant overhead, both in terms of time
      and memory. By initializing privs once per sub, we impose overhead for
      privs which are referenced but not actually used in a subroutine, but
      not for all of the vcl.
      
      Fixes #2708
      f03948f4
    • Poul-Henning Kamp's avatar
      Privatize stuff. · b78a4672
      Poul-Henning Kamp authored
      b78a4672
  7. 28 Aug, 2018 1 commit