TRT-1559:Remove two sets of logs to bring build-log.txt size down #28654
Conversation
|
@DennisPeriquet: This pull request references TRT-1559 which is a valid jira issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
openshift-ci-robot
added
the
jira/valid-reference
openshift-ci
bot
added
the
approved
| @@ -222,8 +222,6 @@ func recordAddOrUpdateEvent( | |||
| Message(message).Build(pathoFrom, to) | |||
|
|
|||
| logrus.WithField("event", *obj).Info("processed event") | |||
| logrus.WithField("locator", interval.StructuredLocator).Info("resulting interval locator") | |||
There was a problem hiding this comment.
Wanna take out the processed event too? i dont see a reason to keep it at this point, nobodys going to be looking for that.
There was a problem hiding this comment.
removed and pushed. thx
DennisPeriquet
force-pushed
the
trt-1559-slow-prow-load
branch
from
08fe098
to
b6ff73e
Compare
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: DennisPeriquet, dgoodwin The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
Job Failure Risk Analysis for sha: b6ff73e
|
|
/test ci/prow/e2e-aws-ovn-serial |
|
@DennisPeriquet: The specified target(s) for
The following commands are available to trigger optional jobs:
Use
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/override ci/prow/e2e-gcp-ovn-upgrade |
|
@DennisPeriquet: Overrode contexts on behalf of DennisPeriquet: ci/prow/e2e-aws-ovn-serial, ci/prow/e2e-gcp-ovn-upgrade In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
@DennisPeriquet: The following tests failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
openshift-merge-bot
bot
merged commit 6632b4a
into
openshift:master
|
[ART PR BUILD NOTIFIER] This PR has been included in build openshift-enterprise-tests-container-v4.16.0-202403261317.p0.g6632b4a.assembly.stream.el8 for distgit openshift-enterprise-tests. |
I believe that a substantially failing job like https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-release-master-nightly-4.15-e2e-metal-ipi-ovn-dualstack/1758641985364692992 yields a rather large (38M)
build-log.txtand browsing to that job takes a long time and consumes an exorbitant amount of RAM (4.6G in my case on chrome) assuming you can successfully load it. Removing these logs could help shrink that file and speed up the prow job loads in general.