From: cel@kernel.org
To: <kdevops@lists.linux.dev>
Cc: Chuck Lever <chuck.lever@oracle.com>
Subject: [PATCH 2/2] gitr: Update default git version to be cloned
Date: Sun, 13 Oct 2024 11:30:53 -0400 [thread overview]
Message-ID: <20241013153053.1431805-2-cel@kernel.org> (raw)
In-Reply-To: <20241013153053.1431805-1-cel@kernel.org>
From: Chuck Lever <chuck.lever@oracle.com>
A few of the git regression tests that passed on Fedora 39 hosts now
fail on Fedora 40. This seems to have been addressed in git-2.46.0,
the latest stable git version as of this writing.
But the newer unit tests seem to require more disk space than the
meager 5GB currently used as the default.
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
---
playbooks/roles/gitr/tasks/main.yml | 2 +-
workflows/gitr/Kconfig | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/playbooks/roles/gitr/tasks/main.yml b/playbooks/roles/gitr/tasks/main.yml
index 2eafeaa2f120..faf1fff75ce0 100644
--- a/playbooks/roles/gitr/tasks/main.yml
+++ b/playbooks/roles/gitr/tasks/main.yml
@@ -183,7 +183,7 @@
export_volname: "{{ gitr_nfs_server_export }}"
export_options: "{{ nfsd_export_options }}"
export_fstype: "{{ gitr_nfs_export_fstype }}"
- export_size: 5g
+ export_size: 10g
export_pnfs: "{{ (gitr_test_group == 'nfs-pnfs') | bool }}"
when:
- gitr_nfs_use_kdevops_nfsd|bool
diff --git a/workflows/gitr/Kconfig b/workflows/gitr/Kconfig
index 05bac614fee3..8de23252208a 100644
--- a/workflows/gitr/Kconfig
+++ b/workflows/gitr/Kconfig
@@ -82,7 +82,7 @@ config GITR_REPO
config GITR_REPO_COMMIT
string "The version of git to check out"
- default "v2.43.0"
+ default "v2.46.0"
help
The commit to be used for the test.
--
2.46.1
prev parent reply other threads:[~2024-10-13 15:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-13 15:30 [PATCH 1/2] fstests: Run the NFS/RDMA section with NFSv4.1 cel
2024-10-13 15:30 ` cel [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=20241013153053.1431805-2-cel@kernel.org \
--to=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