Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • BIND BIND
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 633
    • Issues 633
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 87
    • Merge requests 87
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source ProjectsISC Open Source Projects
  • BINDBIND
  • Merge requests
  • !6375

Fix another kasp test timing issue

  • Review changes

  • Download
  • Patches
  • Plain diff
Merged Matthijs Mekking requested to merge 3362-kasp-system-test-timing-issue into main Jun 01, 2022
  • Overview 1
  • Commits 1
  • Pipelines 2
  • Changes 1

In the cases where we test SOA serial updates and TTL updates, we check if for "all zones loaded" to ensure the new zone content is loaded. But this is the unsigned zone, the signed zone still needs to be produced.

There is thus a timing issue where the dig request comes in before the signing process has finished.

Add a retry quiet to mitigate against it.

Closes #3362 (closed)

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: 3362-kasp-system-test-timing-issue