Skip to content

VIRTWINKVM-2164: Fix Flush Test parameters for HLK1607#945

Merged
kostyanf14 merged 1 commit into
HCK-CI:masterfrom
elizashurov:fix/win2016-flush-test-params
May 5, 2026
Merged

VIRTWINKVM-2164: Fix Flush Test parameters for HLK1607#945
kostyanf14 merged 1 commit into
HCK-CI:masterfrom
elizashurov:fix/win2016-flush-test-params

Conversation

@elizashurov
Copy link
Copy Markdown
Contributor

HLK1607 expects SNMP_IP_ADDRESS and SNMP_PORT, while newer kits use IP and Outlet. Split the test in hcktest.json into two kit entries.

HLK1607 expects SNMP_IP_ADDRESS and SNMP_PORT, while newer kits use
IP and Outlet. Split the test in hcktest.json into two kit entries.

Signed-off-by: Elizabeth Ashurov <eashurov@redhat.com>
@elizashurov elizashurov requested a review from kostyanf14 May 5, 2026 06:53
@elizashurov
Copy link
Copy Markdown
Contributor Author

Resolve:
#837

Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the test configuration for the 'Flush Test' by introducing kit-specific parameters, specifically adding SNMP settings for HLK1607 and restricting standard IP parameters to a defined list of newer HLK versions. Feedback indicates that the explicit list of kits is brittle and likely incomplete, which could lead to regressions for omitted versions; a more robust approach using default settings or exclusion logic was suggested.

Comment on lines +44 to +45
"kits": ["HLK1809", "HLK1809server", "HLK2004", "HLK20H2", "HLK2022", "HLK2025", "HLK2025_next",
"HLK11_22H2", "HLK11_23H2", "HLK11_24H2", "HLK11_25H2", "HLK11_next"],
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

The explicit list of kits for the "Flush Test" parameters is brittle and likely incomplete. It excludes several valid HLK versions (e.g., 1703, 1709, 1803, 1903) and will require manual updates for every future HLK release. Since the original configuration applied to all kits (by having no kits restriction), this change introduces a regression for any kit not explicitly listed here.

If the newer kits can safely ignore the HLK1607-specific parameters, a more robust approach would be to keep the standard parameters in a block with an empty kits array (acting as a default) and provide the HLK1607 overrides in a separate block. If the parameters must be mutually exclusive, consider updating the engine to support a "default" or "exclude" mechanism to avoid maintaining exhaustive lists of all other versions.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good idea, but no "exclude" mechanism for now

Comment on lines +44 to +45
"kits": ["HLK1809", "HLK1809server", "HLK2004", "HLK20H2", "HLK2022", "HLK2025", "HLK2025_next",
"HLK11_22H2", "HLK11_23H2", "HLK11_24H2", "HLK11_25H2", "HLK11_next"],
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like we need a new option for this, but looks good for now

@kostyanf14 kostyanf14 merged commit 42dc15d into HCK-CI:master May 5, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants