public inbox for kdevops@lists.linux.dev
 help / color / mirror / Atom feed
From: Luis Chamberlain <mcgrof@kernel.org>
To: Chuck Lever <cel@kernel.org>, Daniel Gomez <da.gomez@kruces.com>,
	kdevops@lists.linux.dev
Cc: tytso@mit.edu, Luis Chamberlain <mcgrof@kernel.org>
Subject: [PATCH] fstests: collect ${seq}.*.fsx{good,bad,log} results too
Date: Fri, 18 Apr 2025 12:02:48 -0700	[thread overview]
Message-ID: <20250418190248.4182312-1-mcgrof@kernel.org> (raw)

Ted suggests to collect these files too.

Suggested-by: Theodore Ts'o <tytso@mit.edu>
Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
---

I'll let the automatic kdevops CI which will run this after it hits
patchwork run this and see if it works. If it does, then we can apply it.
Every single patch posted to kdevops list triggers a simple fstests
test, and a hit to the kdevops-results-archive --> dashboard.

 playbooks/roles/fstests/tasks/main.yml | 26 ++++++++++++++++++++++++++
 1 file changed, 26 insertions(+)

diff --git a/playbooks/roles/fstests/tasks/main.yml b/playbooks/roles/fstests/tasks/main.yml
index eab35fba026c..e134ee1043dd 100644
--- a/playbooks/roles/fstests/tasks/main.yml
+++ b/playbooks/roles/fstests/tasks/main.yml
@@ -1377,6 +1377,17 @@
     patterns: "*.out.bad"
   register: failed_tests
 
+- name: Look for all other test attribute files
+  tags: [ 'oscheck', 'fstests', 'copy_results', 'test_artifacts' ]
+  become: yes
+  become_flags: 'su - -c'
+  become_method: sudo
+  find:
+    paths: "{{ fstests_data_target }}"
+    recurse: yes
+    patterns: "*.fsx{good,bad,log}"
+  register: test_artifacts
+
 - name: Look for TFB results files
   tags: [ 'copy_results', 'failed_tests', 'tfb' ]
   become: yes
@@ -1472,6 +1483,21 @@
     - not fstests_tfp_copy_enable_list|bool
     - failed_tests.matched > 0
 
+- name: Copy over all other test attribute files for test results
+  tags: [ 'oscheck', 'fstests', 'copy_results', 'copy_final', 'test_artifacts', 'tfb' ]
+  vars:
+    item_path_without_host: "{{ item.path | regex_replace('results') | regex_replace(ansible_host) }}"
+  fetch:
+    src: "{{ item.path }}"
+    dest: "{{ fstests_results_target }}/{{ item_path_without_host | regex_replace(fstests_data_target | regex_escape()) | regex_replace('^/', '') }}"
+    flat: yes
+    validate_checksum: False
+  with_items: "{{ test_artifacts.files }}"
+  loop_control:
+    label: "{{ item.path | regex_replace(fstests_data_target | regex_escape()) | regex_replace('^/', '') }}"
+  when:
+    - test_artifacts.matched > 0
+
 - name: Check if respective bad full file exists
   tags: [ 'oscheck', 'fstests', 'copy_results', 'failed_tests' ]
   become: yes
-- 
2.47.2


                 reply	other threads:[~2025-04-18 19:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20250418190248.4182312-1-mcgrof@kernel.org \
    --to=mcgrof@kernel.org \
    --cc=cel@kernel.org \
    --cc=da.gomez@kruces.com \
    --cc=kdevops@lists.linux.dev \
    --cc=tytso@mit.edu \
    /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