action #118633
closed
coordination #154777: [saga][epic] Shareable os-autoinst and test distribution plugins
coordination #108527: [epic] os-autoinst wheels for scalable code reuse of helper functions and segmented test distributions
coordination #117673: [epic][tools] sporadic "Unable to clone Git repository" for wheels
Re-try on cloning of wheel repositories size:M
Added by livdywan over 1 year ago.
Updated over 1 year ago.
Category:
Feature requests
Description
Motivation¶
Sometimes wheels (or other repos) can't be cloned on the first attempt, see #117673
https://openqa.suse.de/tests/9668977#
[2022-10-06T02:01:46.761898+02:00] [info] ::: OpenQA::Isotovideo::Utils::checkout_git_repo_and_branch: Cloning git URL 'https://github.com/Zaoliang/functional_wheel'
[2022-10-06T02:01:52.973889+02:00] [debug] Cloning into 'functional_wheel'...
fatal: unable to access 'https://github.com/Zaoliang/functional_wheel/': OpenSSL SSL_connect: Connection reset by peer in connection to github.com:443
Acceptance criteria¶
- AC1: Wheels cloning is retried
Suggestions¶
- A reasonable default is used to retry when cloning fails
- Crosscheck how we handle cloning test case and needle repos
- Optional: a maximum retry of N times can be configured in the wheels.yaml or just in test variables
- Category set to Feature requests
- Target version set to Ready
- Copied to action #118882: Make available wheels more discoverable and share knowledge size:S added
Optional: a maximum retry of N times can be configured in the wheels.yaml or just in test variables
This should not be optional, and also not be on test variables but on the wheels.yaml
szarate wrote:
Optional: a maximum retry of N times can be configured in the wheels.yaml or just in test variables
This should not be optional, and also not be on test variables but on the wheels.yaml
We commonly define such settings in openQA test variables. Why do you need it in wheels.yaml?
- Target version changed from Ready to future
- Target version changed from future to Ready
- Status changed from Workable to In Progress
- Assignee set to livdywan
I'll give this a go. Should be pretty straightforward 🤞
- Due date set to 2023-01-18
Setting due date based on mean cycle time of SUSE QE Tools
- Status changed from In Progress to Feedback
Code is merged, which should fullfil AC1. @okurz is going to announce this in #eng-testing in Slack
- Due date deleted (
2023-01-18)
- Status changed from Feedback to Resolved
- Related to action #123556: os-autoinst git cloning of test case repo can fail with auto_review:"fatal.*unable to access.*Connection timed out":retry size:M added
Also available in: Atom
PDF