From: Patrick Steinhardt <ps@pks.im>
To: git@vger.kernel.org
Subject: [PATCH 0/3] Improvements for Perforce tests
Date: Tue, 23 Jul 2024 16:05:33 +0200 [thread overview]
Message-ID: <cover.1721740612.git.ps@pks.im> (raw)
[-- Attachment #1: Type: text/plain, Size: 2700 bytes --]
Hi,
I was recently trying to figure out whether the Perforce tests are
memory-leak free, but noticed that the tests don't run at all on my
machine because I have a newer version of Perforce than our CI. And
because the on-disk depot format has changed since r21, tests are
broken.
This small series adapts tests to work with both r21 and r23, updates
the version of Perforce used in CI and then ultimately marks all of the
Perforce tests as memory-leak free.
Thanks!
Patrick
Patrick Steinhardt (3):
t98xx: fix Perforce tests with p4d r23 and newer
ci: update Perforce version to r23.2
t98xx: mark Perforce tests as memory-leak free
ci/install-dependencies.sh | 2 +-
t/t9800-git-p4-basic.sh | 14 ++++++++++++--
t/t9801-git-p4-branch.sh | 1 +
t/t9802-git-p4-filetype.sh | 16 +++++++++++++---
t/t9803-git-p4-shell-metachars.sh | 1 +
t/t9804-git-p4-label.sh | 1 +
t/t9805-git-p4-skip-submit-edit.sh | 1 +
t/t9806-git-p4-options.sh | 1 +
t/t9808-git-p4-chdir.sh | 1 +
t/t9809-git-p4-client-view.sh | 1 +
t/t9810-git-p4-rcs.sh | 1 +
t/t9811-git-p4-label-import.sh | 1 +
t/t9812-git-p4-wildcards.sh | 1 +
t/t9813-git-p4-preserve-users.sh | 1 +
t/t9814-git-p4-rename.sh | 1 +
t/t9815-git-p4-submit-fail.sh | 1 +
t/t9816-git-p4-locked.sh | 1 +
t/t9817-git-p4-exclude.sh | 1 +
t/t9818-git-p4-block.sh | 1 +
t/t9819-git-p4-case-folding.sh | 1 +
t/t9820-git-p4-editor-handling.sh | 1 +
t/t9821-git-p4-path-variations.sh | 1 +
t/t9822-git-p4-path-encoding.sh | 1 +
t/t9823-git-p4-mock-lfs.sh | 1 +
t/t9825-git-p4-handle-utf16-without-bom.sh | 19 ++++++++++++++++---
t/t9826-git-p4-keep-empty-commits.sh | 1 +
t/t9827-git-p4-change-filetype.sh | 1 +
t/t9828-git-p4-map-user.sh | 1 +
t/t9829-git-p4-jobs.sh | 1 +
t/t9830-git-p4-symlink-dir.sh | 1 +
t/t9831-git-p4-triggers.sh | 1 +
t/t9832-unshelve.sh | 1 +
t/t9833-errors.sh | 1 +
t/t9834-git-p4-file-dir-bug.sh | 1 +
t/t9835-git-p4-metadata-encoding-python2.sh | 1 +
t/t9836-git-p4-metadata-encoding-python3.sh | 1 +
36 files changed, 74 insertions(+), 9 deletions(-)
--
2.46.0.rc1.dirty
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2024-07-23 14:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-23 14:05 Patrick Steinhardt [this message]
2024-07-23 14:05 ` [PATCH 1/3] t98xx: fix Perforce tests with p4d r23 and newer Patrick Steinhardt
2024-07-30 22:41 ` Justin Tobler
2024-07-31 10:28 ` Patrick Steinhardt
2024-07-23 14:05 ` [PATCH 2/3] ci: update Perforce version to r23.2 Patrick Steinhardt
2024-07-24 8:39 ` Johannes Schindelin
2024-07-24 9:01 ` Patrick Steinhardt
2024-07-24 16:10 ` Junio C Hamano
2024-07-30 6:00 ` Patrick Steinhardt
2024-07-30 22:48 ` Justin Tobler
2024-07-31 10:15 ` Patrick Steinhardt
2024-07-23 14:05 ` [PATCH 3/3] t98xx: mark Perforce tests as memory-leak free Patrick Steinhardt
2024-07-30 22:54 ` Justin Tobler
2024-07-31 10:37 ` [PATCH v2 0/3] Improvements for Perforce tests Patrick Steinhardt
2024-07-31 10:37 ` [PATCH v2 1/3] t98xx: fix Perforce tests with p4d r23 and newer Patrick Steinhardt
2024-07-31 10:37 ` [PATCH v2 2/3] ci: update Perforce version to r23.2 Patrick Steinhardt
2024-07-31 10:37 ` [PATCH v2 3/3] t98xx: mark Perforce tests as memory-leak free Patrick Steinhardt
2024-07-31 20:50 ` [PATCH v2 0/3] Improvements for Perforce tests Justin Tobler
2024-07-31 22:32 ` Junio C Hamano
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=cover.1721740612.git.ps@pks.im \
--to=ps@pks.im \
--cc=git@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).