include timestamps in extended test build logs #11564
Conversation
|
[testextended][extended:core(builds)] |
|
lgtm. You might consider the same argument in DumpBuildLogs . There appear to be a few references left to it in the test cases. |
bparees
force-pushed
the
log_timestamps
branch
from
1be1f74 to
e573f16
Compare
|
@jupierce thanks, updated. |
|
Evaluated for origin testextended up to e573f16 |
|
continuous-integration/openshift-jenkins/testextended SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin_extended/690/) (Base Commit: 38c9545) (Extended Tests: core(builds)) |
|
[merge] |
|
continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/10688/) (Image: devenv-rhel7_5250) |
|
Evaluated for origin merge up to e573f16 |
|
[Test]ing while waiting on the merge queue |
|
Evaluated for origin test up to e573f16 |
|
continuous-integration/openshift-jenkins/test SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/10688/) (Base Commit: 8bb33be) |
@jupierce ptal. downside is we'll get double timestamps for builds run w/ high loglevels. upside is we get some timing information for all build logs, which would be useful in debugging this:
#11563