From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: Demi Marie Obenour <demiobenour@gmail.com>
Cc: xen-devel@lists.xenproject.org,
Doug Goldstein <cardoe@cardoe.com>,
Stefano Stabellini <sstabellini@kernel.org>
Subject: Re: [PATCH v1 6/6] [DO NOT MERGE] CI: example how to use ssh to extract logs
Date: Mon, 23 Jun 2025 20:30:10 +0200 [thread overview]
Message-ID: <aFmdMtJQ9pBfMM18@mail-itl> (raw)
In-Reply-To: <c97105b9-9b9d-49a3-8529-4cdd5f85bf4d@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1124 bytes --]
On Mon, Jun 23, 2025 at 02:28:47PM -0400, Demi Marie Obenour wrote:
> On 6/23/25 09:47, Marek Marczykowski-Górecki wrote:
> > ---
> > automation/scripts/qubes-x86-64.sh | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/automation/scripts/qubes-x86-64.sh b/automation/scripts/qubes-x86-64.sh
> > index cf040a29856b..944d0c6d383f 100755
> > --- a/automation/scripts/qubes-x86-64.sh
> > +++ b/automation/scripts/qubes-x86-64.sh
> > @@ -292,6 +292,8 @@ export TEST_LOG="smoke.serial"
> > export TEST_TIMEOUT="$timeout"
> > ./automation/scripts/console.exp | sed 's/\r\+$//'
> > TEST_RESULT=$?
> > +ssh -o StrictHostKeyChecking=no root@$SUT_ADDR xl dmesg || :
> > +ssh -o StrictHostKeyChecking=no root@$SUT_ADDR dmesg || :
> >
> > if [ -n "$retrieve_xml" ]; then
> > nc -w 10 "$SUT_ADDR" 8080 > tests-junit.xml </dev/null
>
> StrictHostKeyChecking=no is generally a bad idea.
> Is there a better option?
It doesn't matter here. It's simply more convenient than a netcat that
is used few lines below.
--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-06-23 18:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-23 13:47 [PATCH v1 0/6] Add infrastructure for testing arbitrary Linux branch, and one more runner Marek Marczykowski-Górecki
2025-06-23 13:47 ` [PATCH v1 1/6] CI: Switch x86 tests to 6.12.34 kernel Marek Marczykowski-Górecki
2025-06-23 20:54 ` Stefano Stabellini
2025-06-23 13:47 ` [PATCH v1 2/6] CI: add AMD Zen 4 HW runner Marek Marczykowski-Górecki
2025-06-23 13:47 ` [PATCH v1 3/6] CI: upload tests-junit.xml as a normal artifact too Marek Marczykowski-Górecki
2025-06-23 20:57 ` Stefano Stabellini
2025-06-23 13:47 ` [PATCH v1 4/6] CI: make test-artifacts branch/job customizable Marek Marczykowski-Górecki
2025-06-23 21:04 ` Stefano Stabellini
2025-06-23 21:30 ` Marek Marczykowski-Górecki
2025-06-23 13:47 ` [PATCH v1 5/6] CI: use Alpine's network setup Marek Marczykowski-Górecki
2025-06-23 20:58 ` Stefano Stabellini
2025-06-23 13:47 ` [PATCH v1 6/6] [DO NOT MERGE] CI: example how to use ssh to extract logs Marek Marczykowski-Górecki
2025-06-23 18:28 ` Demi Marie Obenour
2025-06-23 18:30 ` Marek Marczykowski-Górecki [this message]
2025-06-23 20:58 ` Stefano Stabellini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aFmdMtJQ9pBfMM18@mail-itl \
--to=marmarek@invisiblethingslab.com \
--cc=cardoe@cardoe.com \
--cc=demiobenour@gmail.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.