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
  • !3230

wait for the reply message before checking to avoid false negative.

  • Review changes

  • Download
  • Patches
  • Plain diff
Merged Mark Andrews requested to merge 1676-address-timing-issue-in-forward-system-test-v9_16 into v9_16 Mar 15, 2020
  • Overview 0
  • Commits 1
  • Pipelines 1
  • Changes 1

Waiting for the reply message will ensure that all messages being looked for exist in the logs at the time of checking. When the test was only waiting for the send message there was a race between grep and the ns1 instance of named logging that it had seen the request.

(cherry picked from commit a38a3244)

Closes #1676 (closed)

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: 1676-address-timing-issue-in-forward-system-test-v9_16