-
Notifications
You must be signed in to change notification settings - Fork 260
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
CTS failures - inmemory #7254
Comments
This is not a regression - and can be reproduced on 3.13 as well as 3.14 |
Configuring a local rancher environment with the same 7GBm 2 CPU configuration as github actions led to 1 exception of this type. Inclined to consider this as timing related. A prior fix boosted the retry count in CTS to avoid these. |
Signed-off-by: Nigel Jones <nigel.l.jones+git@gmail.com>
Same issue as seen before. See above PR for timeout increase which hopefully will be sufficient |
The change did not prevent errors occuring on last night's run. |
@cmgrote @mandy-chessell Any thoughts? Beyond that question and reviewing any relevant code, a next step might be to try and run just those tests in a more development oriented environment - possibly needing to introduce delays/latency if we don't figure out why the assets can sometimes not be found - even with a long delay (and no exceptions reporting we've hit the timeout?) |
These (1 typically) continue to occur on the cicd pipeline. This points to a cts framework/parameter issue which needs investigating, presumably timing related. |
This reverts commit f7d94b9. Signed-off-by: Nigel Jones <nigel.l.jones+git@gmail.com>
Revert "#7254 increase poll retry count for cts"
Quick update - Automated CTS ran clean for 2 days, including in memory. On day 3 the inmemory failed, with no relevant code changes, suggesting still some intermittency in this constrained environment |
CTS tests now running cleanly for inmemory. |
The following exceptions are seen when running CTS against the inmemory repository
See also
It does not appear this always occurs, though it does on github actions. Suspect this is timing related.
The text was updated successfully, but these errors were encountered: