Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[QE] limit log size for test reports #4403

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

albfan
Copy link

@albfan albfan commented Oct 16, 2024

Fixes: Issue #4373

Solution/Idea

Reports with long messages are hanging reportportal. Limit its size

Proposed changes

after post process xml report, limit log size

Testing

Tested on log reports long and short than max size

Copy link

openshift-ci bot commented Oct 16, 2024

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign evidolob for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

</xsl:copy>
</xsl:template>

<xsl:template match="failure">
<xsl:copy>
<xsl:value-of select="@message"/>
<xsl:value-of select="substring(@message,0,1000000)"/>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it possible to pick the latest chars from the failure message.. It would have more sense as typically you see the error at the very end

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if the error is at the end...

is there a way to link to the full report or a compressed form?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah, actually seems a combination of both: summary for the error at the beginning ...full trace with logs around the point of the error to the end of the trace.

Copy link
Contributor

@adrianriobo adrianriobo Oct 16, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So this made me think, the problem is about adding too much data on the junit files right?

Because it seems there is another option to import full logs next to results.... (on report portal)

If this is the case may we should see how to avoid the error log to be added on the junit file, for ginkgo AFAIK there are some customization you can do on the reporter to avoid the full trace... on the e2e side I think it is us adding the full error in code.

Can you check this @albfan

Copy link

openshift-ci bot commented Oct 16, 2024

@albfan: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-crc 7748d4e link true /test e2e-crc

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-sigs/prow repository. I understand the commands that are listed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants