Opened 2 years ago

Last modified 12 days ago

#4295 accepted task

Document the process for running Kea version of ISC DHCP "burn-in" tests

Reported by: wlodekwencel Owned by: tmark
Priority: medium Milestone: Kea1.5 QA
Component: tests Version: git
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: N/A
Sub-Project: DHCP Feature Depending on Ticket:
Estimated Difficulty: 0 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no


corresponding ticket to qa ticket:


Change History (9)

comment:1 Changed 2 years ago by tomek

  • Priority changed from medium to low

Decreasing priority to low, will do this in 1.1 beta.

comment:2 Changed 2 years ago by tomek

  • Milestone changed from Kea1.1 to Kea-1.1-final

comment:3 Changed 2 years ago by tomek

  • Milestone changed from Kea-1.1-final to Kea1.1-final

Milestone renamed

comment:4 Changed 23 months ago by tmark

  • Owner set to tmark
  • Status changed from new to accepted

comment:5 Changed 22 months ago by tmark

  • Milestone changed from Kea1.1-final to Kea1.2

comment:6 Changed 16 months ago by tomek

  • Milestone changed from Kea1.2 to Kea1.2-final

comment:7 Changed 15 months ago by tomek

  • Milestone changed from Kea1.2-final to Outstanding Tasks

As discussed on 2017-04-13 call, moving to outstanding.

comment:8 Changed 4 weeks ago by wlodekwencel

  • Milestone changed from Outstanding Tasks to Kea-proposed

comment:9 Changed 12 days ago by tomek

  • Component changed from documentation to tests
  • Milestone changed from Kea-proposed to Kea1.5 QA
  • Priority changed from low to medium
  • Type changed from defect to task

Discussed on 2018-06-28 Kea call. Decision was to ask a list of useful scenarios (such as can Kea survive 24h of traffic without falling over or eating all memory?).

Stephen proposed to run burn-in like tests on recurring basis, rather than just immediately before a release.

Note: See TracTickets for help on using tickets.