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
It appears that logs are not flushed when we write to stdout - if we run a test plan on cluster:k8s we see output in stdout for given test instances via kubectl logs, but those logs do not appear immediately in run.out on the S3 bucket.
There are two parts to this:
flushing on s3bucket daemon (which runs s3fs)
flushing within the testground codebase
The text was updated successfully, but these errors were encountered:
We're likely missing a call to https://godoc.org/go.uber.org/zap#Logger.Sync when the instance shuts down. This should be solved by calling re.logger.SLogger().Sync() from inside RunEnv#Close().
This is not just about flushing at the end of the test. We should flush periodically or after every call to the logger, because if a test deadlocks, we want to be able to get the last emitted logs, even if the buffer is not full.
It appears that logs are not flushed when we write to
stdout
- if we run a test plan oncluster:k8s
we see output instdout
for given test instances viakubectl logs
, but those logs do not appear immediately inrun.out
on the S3 bucket.There are two parts to this:
s3bucket
daemon (which runss3fs
)testground
codebaseThe text was updated successfully, but these errors were encountered: