From: Jakub Kicinski <kuba@kernel.org>
To: Qingfang Deng <dqfext@gmail.com>
Cc: Shuah Khan <shuah@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
Felix Maurer <fmaurer@redhat.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
"Matthieu Baerts (NGI0)" <matttbe@kernel.org>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-ppp@vger.kernel.org, netdev@vger.kernel.org,
Paul Mackerras <paulus@ozlabs.org>
Subject: Re: [PATCH net-next v7] selftests: net: add tests for PPP
Date: Wed, 1 Apr 2026 17:56:21 -0700 [thread overview]
Message-ID: <20260401175621.549c492e@kernel.org> (raw)
In-Reply-To: <CALW65jahWApDnVmFReW+Y3HDxBEmCwzsT1oyh03SW7X5ry6PzA@mail.gmail.com>
On Wed, 1 Apr 2026 23:45:38 +0800 Qingfang Deng wrote:
> > # iperf3: error - unable to connect to server - server may have stopped running or use a different port, firewall issue, etc.: Network is unreachable
> > # TEST: PPPoE [FAIL]
> > not ok 1 selftests: net/ppp: pppoe.sh # exit=1
>
> It looks like pppoe-server fails to start. You may check the syslog to
> see what's going on.
Hm, we don't capture syslog automatically :S We capture stdout and
stderr
I'm not even sure there's something listening on syslog in virtme-ng
Is it possible to make the daemon log to stdout or a file and dump
that file to stdout on failure? Even if we fix the current issue
it will be quite inconvenient if we have to go into syslog every time
the test is failing. The test output should provide enough info to
debug failures.
next prev parent reply other threads:[~2026-04-02 0:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-30 3:55 [PATCH net-next v7] selftests: net: add tests for PPP Qingfang Deng
2026-04-01 15:10 ` Jakub Kicinski
2026-04-01 15:45 ` Qingfang Deng
2026-04-02 0:56 ` Jakub Kicinski [this message]
2026-04-02 2:26 ` Qingfang Deng
2026-04-02 2:52 ` Jakub Kicinski
2026-04-02 9:48 ` Paolo Abeni
2026-04-02 10:13 ` Qingfang Deng
2026-04-02 11:17 ` Paolo Abeni
2026-04-02 12:04 ` Qingfang Deng
2026-04-02 14:37 ` Andrew Lunn
2026-04-02 14:55 ` Jakub Kicinski
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=20260401175621.549c492e@kernel.org \
--to=kuba@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=davem@davemloft.net \
--cc=dqfext@gmail.com \
--cc=edumazet@google.com \
--cc=fmaurer@redhat.com \
--cc=horms@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-ppp@vger.kernel.org \
--cc=matttbe@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=paulus@ozlabs.org \
--cc=shuah@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox