From: Jeff Layton <jlayton@kernel.org>
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: Chuck Lever <cel@kernel.org>,
"kdevops@lists.linux.dev" <kdevops@lists.linux.dev>
Subject: Re: [PATCH v2 0/7] Add a git regression workflow
Date: Thu, 04 Jan 2024 11:46:21 -0500 [thread overview]
Message-ID: <8ee4cfb22491bd377adf882ee3a5e1de325b1593.camel@kernel.org> (raw)
In-Reply-To: <73478566-EE73-46F1-A571-490C22FDD515@oracle.com>
On Thu, 2024-01-04 at 16:04 +0000, Chuck Lever III wrote:
>
> > On Jan 3, 2024, at 1:04 PM, Chuck Lever III <chuck.lever@oracle.com> wrote:
> >
> >
> >
> > > On Jan 3, 2024, at 12:10 PM, Jeff Layton <jlayton@kernel.org> wrote:
> > >
> > > On Wed, 2024-01-03 at 10:08 -0500, Chuck Lever wrote:
> > > > Since the last series, I've added support for tmpfs and NFS mounts,
> > > > in addition to a few other refinements and loads of testing. I'd
> > > > like a little review before I push these.
> > > >
> > >
> > > This all looks pretty great to me. I don't see any need to wait on
> > > merging it, if it seems to be working for you.
> >
> > OK, I'll push later this week.
>
> Blargh.
>
> I pushed the gitr patches this morning, but there are still
> some problems.
>
> I've been trying to run down the NFSv4.1 backchannel problem
> so I haven't run "make gitr-baseline" recently -- I've been
> running the test by hand on the target hosts.
>
> But "make gitr-baseline" is still hitting this error after
> the test passes:
>
> TASK [gitr : Save git regression test output to a file] ************************************************************************************************************************************************
> fatal: [cel]: FAILED! => {"msg": "The task includes an option with an undefined variable. The error was: 'dict object' has no attribute 'stdout_lines'. 'dict object' has no attribute 'stdout_lines'\n\nThe error appears to be in '/home/cel/src/kdevops/playbooks/roles/gitr/tasks/main.yml': line 162, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n- name: Save git regression test output to a file\n ^ here\n"}
>
> I can't seem to nail down why stdout_lines does not exist,
> because sometimes it /does/ exist.
>
> My Ansible fu is not strong.
>
>
---------------8<-------------------
- name: Run the full git regression suite
tags: [ 'run_tests' ]
community.general.make:
chdir: "{{ gitr_mnt }}/git"
target: "test"
jobs: "{{ nproc.stdout }}"
register: gitr_results
failed_when: False
changed_when: False
...
- name: Save git regression test output to a file
tags: [ 'copy_results' ]
ansible.builtin.copy:
content: "{{ gitr_results.stdout_lines|join('\n') }}"
dest: "{{ gitr_mnt }}/gitr.stdout"
---------------8<-------------------
Looking at the first play, you have "failed_when: False". Is it possible
the first play failed and didn't register a result? I'd look closely at
what's happening in that play, in any case...
--
Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2024-01-04 16:46 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-03 15:08 [PATCH v2 0/7] Add a git regression workflow Chuck Lever
2024-01-03 15:08 ` [PATCH v2 1/7] nfsd_add_export: Add an export_options variable Chuck Lever
2024-01-03 15:08 ` [PATCH v2 2/7] nfsd_add_export: Set fsid= on tmpfs exports Chuck Lever
2024-01-03 15:08 ` [PATCH v2 3/7] create_tmpfs: Enable mounting tmpfs file systems for testing Chuck Lever
2024-01-25 14:26 ` Luis Chamberlain
2024-01-25 14:39 ` Chuck Lever III
2024-01-25 15:44 ` Luis Chamberlain
2024-01-03 15:08 ` [PATCH v2 4/7] create_nfs_mount: Enable testing arbitrary NFS mounts Chuck Lever
2024-01-03 15:08 ` [PATCH v2 5/7] Add a playbook for the git regression workflow Chuck Lever
2024-01-25 14:34 ` Luis Chamberlain
2024-01-25 14:41 ` Luis Chamberlain
2024-01-25 15:14 ` Luis Chamberlain
2024-01-25 16:12 ` Chuck Lever III
2024-01-25 16:17 ` Luis Chamberlain
2024-01-03 15:08 ` [PATCH v2 6/7] Add a workflow for the git regression suite Chuck Lever
2024-01-25 15:39 ` Luis Chamberlain
2024-01-25 15:56 ` Luis Chamberlain
2024-01-03 15:09 ` [PATCH v2 7/7] gitr: Adjust the gen_hosts and gen_nodes playbooks Chuck Lever
2024-01-03 17:10 ` [PATCH v2 0/7] Add a git regression workflow Jeff Layton
2024-01-03 18:04 ` Chuck Lever III
2024-01-04 16:04 ` Chuck Lever III
2024-01-04 16:46 ` Jeff Layton [this message]
2024-01-04 18:19 ` Chuck Lever III
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=8ee4cfb22491bd377adf882ee3a5e1de325b1593.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=cel@kernel.org \
--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