Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
Knot Resolver
Knot Resolver
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 141
    • Issues 141
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 17
    • Merge Requests 17
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Knot projects
  • Knot ResolverKnot Resolver
  • Issues
  • #612

Closed
Open
Created Sep 17, 2020 by Tomas Krizek@tkrizekOwner

unify packaging tests

Currently, there are two different implementations of packaging tests:

  • distro/tests

    • depend on external repos (currently OBS)
    • use VMs, because we need to test systemd integration
    • are pretty much exactly what the user would use
    • primarily test default config
  • tests/packaging

    • use docker containers
    • added in !892 (merged) and !947 (merged)
    • test if resolver starts up with given config
    • can't detect certain type of failures (crash shortly after startup, e.g. due to TA update)
    • test loading of optional modules

I think tests/packaging are redundant and they add additional maintenance burden (see my opinion in !947 (comment 154887)). However, they do test that all supported modules can be loaded in config. This functionality should be moved and unified with distro/tests as additional test, so we don't have to maintain two separate implementations of these tests.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None