Logs disappear from logdog after about 2 weeks |
||
Issue description
What steps will reproduce the problem?
(1) ~/.chrome-infra/infra/cipd/logdog -project chromium cat bb/chromium.clang/ToTWin/785/+/recipes/steps/sizes/0/stdout
What is the expected result?
Expect to see log output.
What happens instead?
[I2018-01-24T14:40:58.365492-08:00 221455 0 fetcher.go:366] No logs returned. Sleeping... {"delay":"5s", "index":0}
^C[W2018-01-24T14:40:59.310876-08:00 221455 0 main.go:205] Caught signal; terminating. {"signal":"interrupt"}
[W2018-01-24T14:40:59.311056-08:00 221455 0 fetcher.go:368] Context was canceled. {"error":"context canceled"}
[E2018-01-24T14:40:59.311145-08:00 221455 0 subcommandCat.go:160] Failed to fetch log stream. {"error":"context canceled", "index":0, "path":"bb/chromium.clang/ToTWin/785/+/recipes/stdout", "project":"chromium"}
,
Jan 26 2018
Web UI equivalents: https://ci.chromium.org/buildbot/chromium.clang/ -> https://ci.chromium.org/buildbot/chromium.clang/ToTWin/ -> https://ci.chromium.org/buildbot/chromium.clang/ToTWin/785 -> https://logs.chromium.org/v/?s=chromium%2Fbb%2Fchromium.clang%2FToTWin%2F785%2F%2B%2Frecipes%2Fsteps%2Fsizes%2F0%2Fstdout It gets locked at "0 / 141" for 785 and "0 / 139" for 784. I did a quick bisect and logs for builds [695, 698] and [701, 791] are broken, after are fine but before has a very spotty coverage. I didn't test *all* builds so it may be more broken than that. This looks widespread, and issue 795156 matches the issue description. |
||
►
Sign in to add a comment |
||
Comment 1 by p...@chromium.org
, Jan 24 2018