public inbox for kdevops@lists.linux.dev
 help / color / mirror / Atom feed
From: Scott Mayhew <smayhew@redhat.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: kdevops@lists.linux.dev
Subject: Re: [PATCH 1/2] nfstest: add git-core to the list of install dependencies
Date: Wed, 24 Apr 2024 17:50:58 -0400	[thread overview]
Message-ID: <Zil-wgDyPhsxrmZF@aion> (raw)
In-Reply-To: <Zil3bozkGLbX+822@tissot.1015granger.net>

On Wed, 24 Apr 2024, Chuck Lever wrote:

> On Wed, Apr 24, 2024 at 05:15:10PM -0400, Scott Mayhew wrote:
> > Currently git-core won't be installed if you're running nfstest as a
> > dedicated workflow.
> 
> I don't think it's the "dedicated workflow" that's the problem,
> because I use that all the time. I think I have the "Install
> kernel developer tools" option set or something like that, and
> that pulls in git, trace-cmd, and other stuff.

Ah, maybe that's it.  I have some workflows running where I'm not
building the kernel, so I'm not installing the kernel developer tools.
I'm just installing the latest RHEL8/RHEL9 nightlies and running tests,
and those are where I'm seeing the problem.

I'll tweak the commit message.

-Scott
> 
> But, OK... this is a real dependency for nfstest, so:
> 
> Reviewed-by: Chuck Lever <chuck.lever@oracle.com>
> 
> 
> > Signed-off-by: Scott Mayhew <smayhew@redhat.com>
> > ---
> >  playbooks/roles/nfstest/vars/Debian.yml | 1 +
> >  playbooks/roles/nfstest/vars/RedHat.yml | 1 +
> >  playbooks/roles/nfstest/vars/Suse.yml   | 1 +
> >  3 files changed, 3 insertions(+)
> > 
> > diff --git a/playbooks/roles/nfstest/vars/Debian.yml b/playbooks/roles/nfstest/vars/Debian.yml
> > index cb4cfe5..05d87a2 100644
> > --- a/playbooks/roles/nfstest/vars/Debian.yml
> > +++ b/playbooks/roles/nfstest/vars/Debian.yml
> > @@ -3,3 +3,4 @@ nfstest_packages:
> >    - nfs-common
> >    - python-is-python3
> >    - tcpdump
> > +  - git-core
> > diff --git a/playbooks/roles/nfstest/vars/RedHat.yml b/playbooks/roles/nfstest/vars/RedHat.yml
> > index d8c65fb..a14c20e 100644
> > --- a/playbooks/roles/nfstest/vars/RedHat.yml
> > +++ b/playbooks/roles/nfstest/vars/RedHat.yml
> > @@ -3,3 +3,4 @@ nfstest_packages:
> >    - nfs-utils
> >    - python-unversioned-command
> >    - tcpdump
> > +  - git-core
> > diff --git a/playbooks/roles/nfstest/vars/Suse.yml b/playbooks/roles/nfstest/vars/Suse.yml
> > index 35fcc8e..76adc4d 100644
> > --- a/playbooks/roles/nfstest/vars/Suse.yml
> > +++ b/playbooks/roles/nfstest/vars/Suse.yml
> > @@ -2,3 +2,4 @@
> >  nfstest_packages:
> >    - nfs-utils
> >    - tcpdump
> > +  - git-core
> > -- 
> > 2.44.0
> > 
> > 
> 
> -- 
> Chuck Lever
> 


      reply	other threads:[~2024-04-24 21:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-24 21:15 [PATCH 1/2] nfstest: add git-core to the list of install dependencies Scott Mayhew
2024-04-24 21:15 ` [PATCH 2/2] nfstest: fix another RHEL 8-ism Scott Mayhew
2024-04-24 21:21   ` Chuck Lever
2024-04-24 22:00     ` Scott Mayhew
2024-04-24 22:52       ` Chuck Lever III
2024-04-24 21:19 ` [PATCH 1/2] nfstest: add git-core to the list of install dependencies Chuck Lever
2024-04-24 21:50   ` Scott Mayhew [this message]

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=Zil-wgDyPhsxrmZF@aion \
    --to=smayhew@redhat.com \
    --cc=chuck.lever@oracle.com \
    --cc=kdevops@lists.linux.dev \
    /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