action #118633
closedcoordination #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
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
Updated by okurz about 2 years ago
- Category set to Feature requests
- Target version set to Ready
Updated by livdywan about 2 years ago
- Copied to action #118882: Make available wheels more discoverable and share knowledge size:S added
Updated by szarate about 2 years ago
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
Updated by okurz about 2 years ago
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?
Updated by livdywan almost 2 years ago
- Status changed from Workable to In Progress
- Assignee set to livdywan
I'll give this a go. Should be pretty straightforward 🤞
Updated by openqa_review almost 2 years ago
- Due date set to 2023-01-18
Setting due date based on mean cycle time of SUSE QE Tools
Updated by livdywan almost 2 years ago
Updated by livdywan almost 2 years ago
- 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
Updated by okurz almost 2 years ago
- Due date deleted (
2023-01-18) - Status changed from Feedback to Resolved
https://github.com/os-autoinst/os-autoinst/pull/2238 merged. I pinged about that change in https://suse.slack.com/archives/C02CANHLANP/p1673517402966779
As we don't currently use wheels in os-autoinst-distri-opensuse we shouldn't need to await any verification in production.
Updated by livdywan almost 2 years ago
okurz wrote:
As we don't currently use wheels in os-autoinst-distri-opensuse we shouldn't need to await any verification in production.
Follow-up https://github.com/os-autoinst/os-autoinst/pull/2253 as per feedback in https://suse.slack.com/archives/C02CANHLANP/p1674482162461009
Updated by livdywan almost 2 years ago
- 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