| Summary: | AB-INT: retrieving artifacts over SSH failed | ||
|---|---|---|---|
| Product: | [Infrastructure] AutoBuilder | Reporter: | Alexandre Belloni <alexandre.belloni> |
| Component: | autobuilder | Assignee: | Alexandre Belloni <alexandre.belloni> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium+ | CC: | infras.ab.watcher, Infras.watcher, pidge, randy.macleod |
| Version: | unspecified | ||
| Target Milestone: | 5.2 M1 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | AB-INT | ||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Alexandre Belloni
2024-07-18 13:23:21 UTC
There are some artifact collection code changes in master-next that Alex should be aware of. I discussed a bit the issue with Alexandre, and despite "hung SSH session" likely being the suspect, I do not see how it could happen, considering the parameters passed to ssh commandline in oeqa scripts (connection keepalive and timeout parameters). I did not manage neither to reproduce locally the issue. As Randy mentioned, there has been some changes in the mean time which have reduced the number of ssh connections involved in artifacts retrieval (https://git.yoctoproject.org/poky/commit/?id=6e80b2ab660e60135b52bd7358f0ce7612226f06). Has the issue been observed recently (ie after those changes) ? If not, I suggest to close the issue. Not seen again, closing for now |