DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Juraj Linkeš" <juraj.linkes@pantheon.tech>
To: Jeremy Spewock <jspewock@iol.unh.edu>
Cc: Patrick Robb <probb@iol.unh.edu>,
	Honnappa.Nagarahalli@arm.com, thomas@monjalon.net,
	 lijuan.tu@intel.com, wathsala.vithanage@arm.com, dev@dpdk.org
Subject: Re: [PATCH v7 1/1] dts: add smoke tests
Date: Mon, 17 Jul 2023 13:11:40 +0200	[thread overview]
Message-ID: <CAOb5WZbxmdbpgMUpUMp6FXP+z5C-Ks7hzzELXGLnR-WXWifZfw@mail.gmail.com> (raw)
In-Reply-To: <CAAA20URs-ALokoUvg86m3WqL5XDGQ+DrGSOO1Fu-OSKryCZU0Q@mail.gmail.com>

On Sat, Jul 15, 2023 at 1:25 AM Jeremy Spewock <jspewock@iol.unh.edu> wrote:
>
>
>
> On Fri, Jul 14, 2023 at 11:30 AM Juraj Linkeš <juraj.linkes@pantheon.tech> wrote:
>>
>> On Fri, Jul 14, 2023 at 4:47 PM Patrick Robb <probb@iol.unh.edu> wrote:
>> >
>> >
>> > Tested-by: Patrick Robb <probb@iol.unh.edu>
>>
>> Have you tested with a non-root user? The unit tests are failing for me.
>
>
> We have been running this as root in testing and there is an issue with running this as non-root users because the unit tests don't escalate privileges. This is a trivial fix of course, but in further testing I think it also makes sense to extend the timeouts for these unit tests (as we do in regular CI testing) and I will wrap this into an updated patch on Monday morning.

Since you'll be sending another version, I'll send some more comments,
so please wait for those. I want to mention one thing beforehand - I
needed a Python interactive session so I added it and modified what I
needed/saw fit. Please see
http://patches.dpdk.org/project/dpdk/patch/20230717110709.39220-5-juraj.linkes@pantheon.tech/
and use what's in it if you want. More coming later in the
aforementioned comments.

Thanks,
Juraj

  reply	other threads:[~2023-07-17 11:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-13 16:53 [PATCH v7 0/1] Add DTS " jspewock
2023-07-13 16:53 ` [PATCH v7 1/1] dts: add " jspewock
2023-07-13 18:48   ` Jeremy Spewock
2023-07-14  7:34   ` Juraj Linkeš
2023-07-14 14:47     ` Patrick Robb
2023-07-14 15:29       ` Juraj Linkeš
2023-07-14 23:25         ` Jeremy Spewock
2023-07-17 11:11           ` Juraj Linkeš [this message]
2023-07-17 14:50   ` Juraj Linkeš
2023-07-17 19:30     ` Jeremy Spewock
2023-07-18  9:55       ` Juraj Linkeš

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=CAOb5WZbxmdbpgMUpUMp6FXP+z5C-Ks7hzzELXGLnR-WXWifZfw@mail.gmail.com \
    --to=juraj.linkes@pantheon.tech \
    --cc=Honnappa.Nagarahalli@arm.com \
    --cc=dev@dpdk.org \
    --cc=jspewock@iol.unh.edu \
    --cc=lijuan.tu@intel.com \
    --cc=probb@iol.unh.edu \
    --cc=thomas@monjalon.net \
    --cc=wathsala.vithanage@arm.com \
    /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;
as well as URLs for NNTP newsgroup(s).