Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • BIND BIND
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 528
    • Issues 528
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 95
    • Merge requests 95
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & 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 Projects
  • BINDBIND
  • Issues
  • #66
Closed
Open
Created Feb 16, 2018 by Michał Kępień@michalOwner

ixfr system test fails intermittently

Two different failure modes, both seem to be related to timing at first glance:

  • https://gitlab.isc.org/isc-projects/bind9/-/jobs/1050
  • https://gitlab.isc.org/isc-projects/bind9/-/jobs/1092
S:ixfr:Thu Feb 15 19:54:14 UTC 2018
T:ixfr:1:A
A:System test ixfr
I:testing initial AXFR
server reload successful
I:testing successful IXFR
zone refresh queued
I:testing AXFR fallback after IXFR failure
zone refresh queued
I:testing ixfr-from-differences option
server reload successful
I:failed to get incremental response
I:testing request-ixfr option in view vs zone
I: this result should be AXFR
server reload successful
I: this result should be AXFR
I:  success: AXFR it was
I: this result should be IXFR
server reload successful
I:  success: IXFR it was
I:testing DiG's handling of a multi message AXFR style IXFR response
I:test 'dig +notcp ixfr=<value>' vs 'dig ixfr=<value> +notcp' vs 'dig ixfr=<value>'
I:exit status: 1
R:FAIL
E:ixfr:Thu Feb 15 19:54:51 UTC 2018
  • https://gitlab.isc.org/isc-projects/bind9/-/jobs/1083
  • https://gitlab.isc.org/isc-projects/bind9/-/jobs/1095
  • https://gitlab.isc.org/isc-projects/bind9/-/jobs/1129
S:ixfr:Thu Feb 15 23:40:59 UTC 2018
T:ixfr:1:A
A:System test ixfr
I:testing initial AXFR
server reload successful
I:testing successful IXFR
zone refresh queued
I:testing AXFR fallback after IXFR failure
zone refresh queued
I:testing ixfr-from-differences option
server reload successful
I:testing request-ixfr option in view vs zone
I: this result should be AXFR
server reload successful
I: this result should be AXFR
I:failed to get nonincremental response in 2nd AXFR test
I: this result should be IXFR
server reload successful
I:  success: IXFR it was
I:testing DiG's handling of a multi message AXFR style IXFR response
I:test 'dig +notcp ixfr=<value>' vs 'dig ixfr=<value> +notcp' vs 'dig ixfr=<value>'
I:exit status: 1
R:FAIL
E:ixfr:Thu Feb 15 23:41:29 UTC 2018

I grabbed the test artifacts from all the jobs listed above lest they get removed.

Edited Feb 16, 2018 by Michał Kępień
Assignee
Assign to
Time tracking