Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • BIND BIND
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 530
    • Issues 530
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 101
    • Merge requests 101
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • 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
  • #2098

Closed
Open
Created Aug 25, 2020 by Ondřej Surý@ondrejOwner0 of 1 task completed0/1 task

Move wire_test to standalone tool with man page and such...

The following discussion from !4006 (closed) should be addressed:

  • @each started a discussion: (+3 comments)

    We did this a while ago, but I had to revert it (see commit e45be9d1). It's used for fuzz testing as well as system tests. I also use it myself sometimes for converting DNS data to and from wire format, and I know I'm not the only one because someone at infoblox asked me to restore it as part of the regular build instead of the test build.

    Rather than moving it to bin/tests/system I wonder if we should consider putting it in bin/tools, like we did with named-journalprint or named-rrchecker or nsec3hash.

Assignee
Assign to
Time tracking