You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 20, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Mar 20, 2026. It is now read-only.
Disabling all debug options with helm and chart-testing still can end up with a test that times out or fails.
The timeout can occur when printing the log output while running make e2e. It always seems to eithe r get stuck/timeout after printing logs for timescaledb.
This is the issue I am seeing locally and with Github Actions reported here and then fixed here. I will attempt to remedy it by applying the new kubectl-timeout configuration option and see if that helps.
ct does seem to have big issues when printing out logs over a specific line count. Adding in the kubectl-timeout doesn't really help the issue. The main issue I can find with all various amount of testing is that ct will 100% stop working when printing out the logs from the timescaledb pod. This is the only pod which the logs are quite extensive. Even setting the logging level to 0, doesn't keep the logs from being printed so either way ct will just stop working indefinitely or until there is some timeout limit reached (320m) in Github Actions.
Activity
nhudson commentedon Sep 1, 2022
Disabling all debug options with
helmandchart-testingstill can end up with a test that times out or fails.The timeout can occur when printing the log output while running
make e2e. It always seems to eithe r get stuck/timeout after printing logs for timescaledb.nhudson commentedon Sep 13, 2022
This is the issue I am seeing locally and with Github Actions reported here and then fixed here. I will attempt to remedy it by applying the new
kubectl-timeoutconfiguration option and see if that helps.nhudson commentedon Sep 13, 2022
ctdoes seem to have big issues when printing out logs over a specific line count. Adding in thekubectl-timeoutdoesn't really help the issue. The main issue I can find with all various amount of testing is thatctwill 100% stop working when printing out the logs from the timescaledb pod. This is the only pod which the logs are quite extensive. Even setting the logging level to 0, doesn't keep the logs from being printed so either wayctwill just stop working indefinitely or until there is some timeout limit reached (320m) in Github Actions.nhudson commentedon Sep 14, 2022
I created an issue upstream helm/chart-testing#471 that details what I am seeing with our use of
ct.I also created PR to add the config option to disable printing of the logs to stdout here: helm/chart-testing#472
nhudson commentedon Sep 14, 2022
I have started using my patched version of
ctwith success with this tobs PR: #579nhudson commentedon Dec 7, 2022
This has been fixed.