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

Cirrus: Collect ginkgo node logs artifacts #9113

Merged

Conversation

cevich
Copy link
Member

@cevich cevich commented Jan 26, 2021

In rare cases, it's possible for one of the ginkgo processes to "hang".
When this occurs, the main output will contain this message:

Ginkgo timed out waiting for all parallel nodes to report

The only way to debug this was to look through concatenated printing
of the ginkgo node logs. This is a tedious and daunting task,
requiring special search knowledge, facing a "wall of text".

Simplify the situation by collecting the node logs separately, as
individual files in a cirrus-artifact. In this way, it's faster to
figure out which test "hung" by examining each log individually. The
log file which does not have a pass/fail summary at the end,
indicates the last test hung (for whatever reason), and includes it's
output (if any).

Signed-off-by: Chris Evich [email protected]

@cevich cevich force-pushed the ginkgo_logs_artifact branch 3 times, most recently from c38ae33 to 3137db4 Compare January 26, 2021 21:14
@cevich
Copy link
Member Author

cevich commented Jan 27, 2021

@rhatdan
Copy link
Member

rhatdan commented Jan 27, 2021

LGTM

@cevich cevich requested a review from edsantiago February 2, 2021 14:35
@cevich
Copy link
Member Author

cevich commented Feb 2, 2021

@edsantiago PTAL...should be easy one.

@edsantiago
Copy link
Member

Unfortunate that Cirrus does not offer an option to flatten the directory structure.

Do you know why logs weren't collected for any of the remote jobs? Should they have been?

@edsantiago
Copy link
Member

I will assume that ginkgo logs don't exist for remoteintegration: https://cirrus-ci.com/task/5075101865476096?command=ginkgo_node_logs#L1

cat: '/var/tmp/go/src/github.com/containers/podman/test/e2e/ginkgo-node-*.log': No such file or directory

/lgtm
/hold

@openshift-ci-robot openshift-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 2, 2021
@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Feb 2, 2021
@cevich
Copy link
Member Author

cevich commented Feb 2, 2021

Unfortunate that Cirrus does not offer an option to flatten the directory structure.

No the only option is to move the around relative to $CIRRUS_WORKING_DIR 😞

I will assume that ginkgo logs don't exist for remoteintegration

Interesting...I believe it's because there is no -debug flag used for that target's command-line. I can add that in a separate PR if you think it's important.

@edsantiago
Copy link
Member

Already done, #9200

@cevich
Copy link
Member Author

cevich commented Feb 2, 2021

Oh! Correction: This is because ginkgo-remote does not use multiple threads (nodes) for testing. So the log file would be 100% identical to what you see for the regular output.

In rare cases, it's possible for one of the ginkgo processes to "hang".
When this occurs, the main output will contain this message:

``Ginkgo timed out waiting for all parallel nodes to report``

The only way to debug this was to look through concatenated printing
of the ginkgo node logs.  This is a tedious and daunting task,
requiring special search knowledge, facing a "wall of text".

Simplify the situation by collecting the node logs separately, as
individual files in a cirrus-artifact.  In this way, it's faster to
figure out which test "hung" by examining each log individually.  The
log file which does not have a pass/fail summary at the end,
indicates the last test hung (for whatever reason), and includes it's
output (if any).

Signed-off-by: Chris Evich <[email protected]>
@cevich cevich force-pushed the ginkgo_logs_artifact branch from 3137db4 to 6a6e868 Compare February 3, 2021 15:52
@openshift-ci-robot openshift-ci-robot removed the lgtm Indicates that a PR is ready to be merged. label Feb 3, 2021
@cevich
Copy link
Member Author

cevich commented Feb 3, 2021

Rebased w/ Ed's fix.

@edsantiago
Copy link
Member

@edsantiago
Copy link
Member

/lgtm
/hold

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Feb 3, 2021
@openshift-ci-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cevich, edsantiago

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 3, 2021
@rhatdan
Copy link
Member

rhatdan commented Feb 4, 2021

/hold cancel

@openshift-ci-robot openshift-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 4, 2021
@openshift-merge-robot openshift-merge-robot merged commit e6e3520 into containers:master Feb 4, 2021
@cevich cevich deleted the ginkgo_logs_artifact branch June 30, 2021 18:08
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 22, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 22, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants