-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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: Produce and collect varlink output #4222
Cirrus: Produce and collect varlink output #4222
Conversation
@edsantiago PTAL when u have a mo. I believe I got the redirect correct. Not sure I'm happy about the collection condition, but want to let the tests run to see how it works out... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some nits. Mostly LGTM, thank you for catching this.
2652b27
to
10a2c6e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. The conditional in the Makefile is scary but I guess a good idea to avoid leaving logs on dev systems.
When executing 'make remotesystem' testing, a varlink process is started up but it's stdio is dumped due to the production of excessive data. However, this also means if the process has a problem, any errors will not be accessible. Instead, grab only the last 100 lines and direct them into a file. Also update automation's log collection to retrieve this file when the `$REMOTE_CLIENT` env. var. is `true`. Signed-off-by: Chris Evich <[email protected]>
10a2c6e
to
ffe726e
Compare
Thanks for the collaboration @edsantiago I think I've got all the tweaks and suggestions packaged up, hopefully tests will show this working... |
Tests pass (after the usual re-run of flakes). I see varlink.log in some runs, also see "no such file or directory" in others. What I don't see is failures in podman-varlink not running :-( |
@edsantiago that's okay, I've only seen that in #3901 under the new F31 (beta) VM. Once this merges I'll rebase that and hopefully we'll catch something useful. |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cevich, edsantiago, mheon 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 |
Changes LGTM |
/lgtm |
When executing 'make remotesystem' testing, a varlink process is started
up but it's stdio is dumped due to the production of excessive data.
However, this also means if the process has a problem, any errors will
not be accessible.
Instead, grab only the last 100 lines and direct them into a file. Also
update automation's log collection to retrieve this file when the
$REMOTE_CLIENT
env. var. istrue
.Signed-off-by: Chris Evich [email protected]