1. 21 Mar, 2019 8 commits
  2. 20 Mar, 2019 11 commits
    • Michał Kępień's avatar
      Fix key ID extraction in the "dnssec" system test · a40c60e4
      Michał Kępień authored
      Simply looking for the key ID surrounded by spaces in the tested
      dnssec-signzone output file is not a precise enough method of checking
      for signatures prepared using a given key ID: it can be tripped up by
      cross-algorithm key ID collisions and certain low key IDs (e.g. 60, the
      TTL specified in bin/tests/system/dnssec/signer/example.db.in), which
      triggers false positives for the "dnssec" system test.  Make key ID
      extraction precise by using an awk script which operates on specific
    • Michał Kępień's avatar
      Merge branch 'michal/minor-mirror-system-test-tweaks' into 'master' · a17aff74
      Michał Kępień authored
      Minor "mirror" system test tweaks
      See merge request !1713
    • Michał Kępień's avatar
      Increase dig query timeout to 2 seconds · 73afbdc5
      Michał Kępień authored
      The "mirror" system test expects all dig queries (including recursive
      ones) to be responded to within 1 second, which turns out to be overly
      optimistic in certain cases and leads to false positives being
      triggered.  Increase dig query timeout used throughout the "mirror"
      system test to 2 seconds in order to alleviate the issue.
    • Michał Kępień's avatar
      Increase TAT query interval · 6847a29b
      Michał Kępień authored
      Currently, ns3 in the "mirror" system test sends trust anchor telemetry
      queries every second as it is started with "-T tat=1".  Given the number
      of trust anchors configured on ns3 (9), TAT-related traffic clutters up
      log files, hindering troubleshooting efforts.  Increase TAT query
      interval to 3 seconds in order to alleviate the issue.
      Note that the interval chosen cannot be much higher if intermittent test
      failures are to be avoided: TAT queries are only sent after the
      configured number of seconds passes since resolver startup.  Quick
      experiments show that even on contemporary hardware, ns3 should be
      running for at least 5 seconds before it is first shut down, so a
      3-second TAT query interval seems to be a reasonable, future-proof
      compromise.  Ensure the relevant check is performed before ns3 is first
      shut down to emphasize this trade-off and make it more clear by what
      time TAT queries are expected to be sent.
    • Ondřej Surý's avatar
      Merge branch '4-update-gitignore-for-future-automake' into 'master' · c6b03841
      Ondřej Surý authored
      Update and sort the top level .gitignore to ignore automake files
      See merge request !1727
    • Ondřej Surý's avatar
      Sort the top level .gitignore file · b9d524ed
      Ondřej Surý authored
    • Ondřej Surý's avatar
    • Michał Kępień's avatar
      Merge branch 'michal/serve-stale-system-test-wait-for-dump-completion' into 'master' · abbdf3d7
      Michał Kępień authored
      "serve-stale" system test: wait until "rndc dumpdb" completes
      See merge request !1712
    • Michał Kępień's avatar
      Wait until "rndc dumpdb" completes · 6e3f812a
      Michał Kępień authored
      "rndc dumpdb" works asynchronously, i.e. the requested dump may not yet
      be fully written to disk by the time "rndc" returns.  Prevent false
      positives for the "serve-stale" system test by only checking dump
      contents after the line indicating that it is complete is written.
    • Mark Andrews's avatar
      Merge branch 'placeholder' into 'master' · cde8df8b
      Mark Andrews authored
      See merge request !1724
    • Mark Andrews's avatar
      placeholder · 2bddb0e2
      Mark Andrews authored
  3. 19 Mar, 2019 21 commits