All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: Luis Chamberlain <mcgrof@kernel.org>,
	 Daniel Gomez <da.gomez@samsung.com>,
	Chuck Lever <cel@kernel.org>
Cc: kdevops@lists.linux.dev, Jeff Layton <jlayton@kernel.org>
Subject: [PATCH v2 3/5] gitr: enable verbose logging in the test harness
Date: Thu, 18 Jun 2026 08:17:17 -0400	[thread overview]
Message-ID: <20260618-fixes-v2-3-c8bab773a55e@kernel.org> (raw)
In-Reply-To: <20260618-fixes-v2-0-c8bab773a55e@kernel.org>

It's pretty difficult to suss out what failed when the gitr suite fails.
Make it do verbose logging so that there is some indication of what
failed when it does occur.

Signed-off-by: Jeff Layton <jlayton@kernel.org>
---
 playbooks/roles/gitr/tasks/main.yml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/playbooks/roles/gitr/tasks/main.yml b/playbooks/roles/gitr/tasks/main.yml
index cd4402deec90..c9c1d5b4e82c 100644
--- a/playbooks/roles/gitr/tasks/main.yml
+++ b/playbooks/roles/gitr/tasks/main.yml
@@ -265,7 +265,7 @@
   environment:
     GIT_TEST_CLONE_2GB: "true"
   ansible.builtin.shell:
-    cmd: "prove -Q -a /tmp/{{ gitr_run_uniqifier }}.tgz --jobs {{ gitr_test_thread_count }} ./t[0-9]*.sh"
+    cmd: "prove -Q -a /tmp/{{ gitr_run_uniqifier }}.tgz --jobs {{ gitr_test_thread_count }} ./t[0-9]*.sh :: --verbose-log"
     chdir: "{{ gitr_mnt }}/git/t"
   register: gitr_results
   failed_when: false
@@ -274,7 +274,7 @@
 - name: Run specific git regression tests
   tags: run_specific_tests
   ansible.builtin.command:
-    cmd: "prove -Q -a /tmp/{{ gitr_run_uniqifier }}.tgz {{ gitr_test_list }}"
+    cmd: "prove -Q -a /tmp/{{ gitr_run_uniqifier }}.tgz {{ gitr_test_list }} :: --verbose-log"
     chdir: "{{ gitr_mnt }}/git/t"
   register: gitr_results
   failed_when: false

-- 
2.54.0


  parent reply	other threads:[~2026-06-18 12:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-18 12:17 [PATCH v2 0/5] kdevops: fixes for new ansible and some nfsd default config changes Jeff Layton
2026-06-18 12:17 ` [PATCH v2 1/5] ansible: fix bare conditionals for ansible-core 2.20+ strict booleans Jeff Layton
2026-06-18 12:17 ` [PATCH v2 2/5] ansible: replace deprecated top-level ansible_* facts with ansible_facts[] Jeff Layton
2026-06-18 12:17 ` Jeff Layton [this message]
2026-06-18 12:17 ` [PATCH v2 4/5] nfsd: use more reasonable defaults for local VM testing Jeff Layton
2026-06-18 12:17 ` [PATCH v2 5/5] devconfig: add some extra packages to the kdev tools Jeff Layton

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=20260618-fixes-v2-3-c8bab773a55e@kernel.org \
    --to=jlayton@kernel.org \
    --cc=cel@kernel.org \
    --cc=da.gomez@samsung.com \
    --cc=kdevops@lists.linux.dev \
    --cc=mcgrof@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 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.