Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TE-11.3,RT-1.10: configure default NI name #2548

Merged
merged 4 commits into from
Feb 16, 2024

Conversation

kjahed
Copy link
Contributor

@kjahed kjahed commented Jan 15, 2024

Use fptest.ConfigureDefaultNetworkInstance to make sure NI name is configured when replacing default NI.

@kjahed kjahed requested review from a team as code owners January 15, 2024 22:18
@kjahed kjahed requested review from a team and thesrinath January 15, 2024 22:18
@AmrNJ
Copy link
Contributor

AmrNJ commented Feb 12, 2024

Please can you rebase?

@coveralls
Copy link

Pull Request Test Coverage Report for Build 7874829035

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 52.281%

Totals Coverage Status
Change from base Build 7869443570: 0.0%
Covered Lines: 1673
Relevant Lines: 3200

💛 - Coveralls

@self-maurya self-maurya merged commit dd9eed3 into openconfig:main Feb 16, 2024
11 checks passed
frasieroh pushed a commit to aristanetworks/openconfig-featureprofiles that referenced this pull request Feb 16, 2024
* use util function to configure default ni

* revert benchmarking test
ANISH-GOTTAPU pushed a commit to open-traffic-generator/featureprofiles that referenced this pull request Jul 10, 2024
* use util function to configure default ni

* revert benchmarking test
bkreddy143 pushed a commit to nokia/featureprofiles that referenced this pull request Jul 17, 2024
* use util function to configure default ni

* revert benchmarking test
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants