Skip to content

Add TH5 ASIC type for QoS Tests#13230

Merged
StormLiangMS merged 1 commit intosonic-net:masterfrom
ccroy-arista:add-th5-to-asic-type-list-for-qos
Jun 13, 2024
Merged

Add TH5 ASIC type for QoS Tests#13230
StormLiangMS merged 1 commit intosonic-net:masterfrom
ccroy-arista:add-th5-to-asic-type-list-for-qos

Conversation

@ccroy-arista
Copy link
Contributor

The TH5 ASIC type is being added to the qos base test file here so it can be properly identified during testing,
such as in the case of test_qos_sai.py.

Summary:
Fixes https://github.com/aristanetworks/sonic-qual.msft/issues/137

Type of change

  • Bug fix
  • Testbed and Framework(new/improvement)
  • Test case(new/improvement)

Back port request

  • 202012
  • 202205
  • 202305
  • 202311
  • 202405

Approach

What is the motivation for this PR?

Proper identification of the TH5 ASIC for qos tests.

How did you verify/test it?

Verified that the error "Cannot identify DUT ASIC type" no longer occurs when running test_qos_sai.py (the test advances beyond this point of failure now).

See aristanetworks/sonic-qual.msft/issues/137
(ASIC type is incorrectly identified as jr2).

In conjunction with the addition of the
Quicksilver HW SKUs (occurring in a separate
pull request) the TH5 ASIC type is being
added to the qos base test file here so it
can be properly identified during testing,
such as in the case of test_qos_sai.py.
@ccroy-arista ccroy-arista marked this pull request as ready for review June 11, 2024 20:41
Copy link
Collaborator

@StormLiangMS StormLiangMS left a comment

Choose a reason for hiding this comment

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

LGTM

@StormLiangMS StormLiangMS merged commit 2543118 into sonic-net:master Jun 13, 2024
mssonicbld pushed a commit to mssonicbld/sonic-mgmt that referenced this pull request Jun 13, 2024
See aristanetworks/sonic-qual.msft/issues/137
(ASIC type is incorrectly identified as jr2).

In conjunction with the addition of the
Quicksilver HW SKUs (occurring in a separate
pull request) the TH5 ASIC type is being
added to the qos base test file here so it
can be properly identified during testing,
such as in the case of test_qos_sai.py.
@mssonicbld
Copy link
Collaborator

Cherry-pick PR to 202311: #13261

@StormLiangMS
Copy link
Collaborator

hi @bingwang-ms for 202405 cherry pick.

mssonicbld pushed a commit that referenced this pull request Jun 13, 2024
See aristanetworks/sonic-qual.msft/issues/137
(ASIC type is incorrectly identified as jr2).

In conjunction with the addition of the
Quicksilver HW SKUs (occurring in a separate
pull request) the TH5 ASIC type is being
added to the qos base test file here so it
can be properly identified during testing,
such as in the case of test_qos_sai.py.
@ccroy-arista
Copy link
Contributor Author

Awaiting cherry-pick to 202405.

mssonicbld pushed a commit to mssonicbld/sonic-mgmt that referenced this pull request Jun 18, 2024
See aristanetworks/sonic-qual.msft/issues/137
(ASIC type is incorrectly identified as jr2).

In conjunction with the addition of the
Quicksilver HW SKUs (occurring in a separate
pull request) the TH5 ASIC type is being
added to the qos base test file here so it
can be properly identified during testing,
such as in the case of test_qos_sai.py.
@mssonicbld
Copy link
Collaborator

Cherry-pick PR to 202405: #13348

mssonicbld pushed a commit that referenced this pull request Jun 18, 2024
See aristanetworks/sonic-qual.msft/issues/137
(ASIC type is incorrectly identified as jr2).

In conjunction with the addition of the
Quicksilver HW SKUs (occurring in a separate
pull request) the TH5 ASIC type is being
added to the qos base test file here so it
can be properly identified during testing,
such as in the case of test_qos_sai.py.
@ccroy-arista ccroy-arista deleted the add-th5-to-asic-type-list-for-qos branch November 7, 2024 18:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants