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

Fix: Update validation-tests.yml pipenv install issues #1080

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

Mionsz
Copy link
Collaborator

@Mionsz Mionsz commented Feb 11, 2025

Fix: Update validation-tests.yml pipenv install issues

@Mionsz Mionsz marked this pull request as ready for review February 11, 2025 14:44
@Mionsz Mionsz force-pushed the validation-automation-install-pipenv branch 15 times, most recently from c07c278 to 5855a2b Compare February 12, 2025 07:09
.github/workflows/validation-tests.yml Show resolved Hide resolved
.github/workflows/validation-tests.yml Show resolved Hide resolved
.github/workflows/validation-tests.yml Show resolved Hide resolved
@zLukas
Copy link
Collaborator

zLukas commented Feb 12, 2025

In my opionion, we should be able to run it loccally then use GHA as executor. This approach have two main benefits:

  • you are independent from GHA (f.e. when gh is temporary down) , you can run it anywhere, and it's more flexible.
  • fixing workflow is easier locally rather than in gha yaml file, as you have more debugging, local testing options and more people might have a chance to fix if they do not feel confortable with GHA.

so my suggextion is to keep inputs, and triggers as it is, but encapsule/merge (to some extent) run steps to scripts that are kept in repo.

Fix: Update validation-tests.yml pipenv  install issues and run issues
Add: Multiple test cases run inputs
Add: Dropdown for pre-release use cases
Add: Fixtures.py time.sleep between runs
Signed-off-by: Milosz Linkiewicz <[email protected]>
Fix: Fixed overall pytest/workflow run success rate by using single cases and retry approach
Feature: Working inputs.validation-tests-2 input
Feature: Type of bonding to use for validation run (Validation-iface-binding)
Feature: Type of port_p and port_r to use for validation run (validation-test-port-p, validation-test-port-r)

Signed-off-by: Milosz Linkiewicz <[email protected]>
Fixed: Set an timeout to 12h as tests can be lengthy

Signed-off-by: Milosz Linkiewicz <[email protected]>
@Mionsz Mionsz force-pushed the validation-automation-install-pipenv branch from 5855a2b to 3517e9f Compare February 12, 2025 15:44
Refactor: Moved validation tests run to script file
Signed-off-by: Milosz Linkiewicz <[email protected]>
@Mionsz Mionsz force-pushed the validation-automation-install-pipenv branch 2 times, most recently from 82249e0 to 88e0ec0 Compare February 12, 2025 18:12
@Mionsz Mionsz force-pushed the validation-automation-install-pipenv branch from 88e0ec0 to 5793ddb Compare February 13, 2025 09:17
Signed-off-by: Milosz Linkiewicz <[email protected]>
@Mionsz Mionsz force-pushed the validation-automation-install-pipenv branch from 5793ddb to 9d9a2c1 Compare February 13, 2025 10:10
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