From: M Hickford <mirth.hickford@gmail.com>
To: Git Mailing List <git@vger.kernel.org>
Cc: Patrick Steinhardt <ps@pks.im>, soekkle@freenet.de
Subject: "meson test" very slow on Windows
Date: Sat, 1 Feb 2025 22:56:53 +0000 [thread overview]
Message-ID: <CAGJzqsmmq1R9_q=p_AsuFMFr3UzyQ4H186CpfWTnCoAnHu_OXA@mail.gmail.com> (raw)
Hi. Has anyone else found that "meson test" is very slow on Windows? I
built Git using "meson compile" with compiler MSVC and backend ninja.
Curiously the first few tests were fast. Test 20 (exact number varies)
and later were slow:
1/1029 unit-tests OK
2.11s
2/1029 t-example-decorate OK
1.45s
3/1029 t-hash OK
1.32s
4/1029 t-hashmap OK
1.24s
5/1029 t-mem-pool OK
1.16s
6/1029 t-oid-array OK
1.10s
7/1029 t-oidmap OK
1.05s
8/1029 t-oidtree OK
0.98s
9/1029 t-prio-queue OK
0.94s
10/1029 t-reftable-basics OK
0.89s
11/1029 t-reftable-block OK
0.83s
12/1029 t-reftable-merged OK
0.77s
13/1029 t-reftable-pq OK
0.72s
14/1029 t-reftable-reader OK
0.64s
15/1029 t-reftable-readwrite OK
0.54s
16/1029 t-reftable-record OK
0.45s
17/1029 t-reftable-tree OK
0.29s
18/1029 t-strbuf OK
0.20s
19/1029 t-strcmp-offset OK
0.51s
20/1029 t-trailer OK
5.40s
21/1029 t-urlmatch-normalization OK
5.32s
22/1029 t-reftable-stack OK
17.67s
23/1029 t0013-sha1dc OK
42.50s
24/1029 t0004-unwritable OK
46.87s
25/1029 t0022-crlf-rename OK
43.77s
26/1029 t0014-alias OK
49.05s
27/1029 t0023-crlf-am OK
32.28s
28/1029 t0005-signals OK
49.83s
29/1029 t0018-advice OK
58.71s
30/1029 t0010-racy-git OK
64.75s
On Linux, all tests were fast as expected.
I built at commit 58b5801aa9 (The sixth batch, 2025-01-31)
Any ideas?
next reply other threads:[~2025-02-01 22:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-01 22:56 M Hickford [this message]
2025-02-02 7:46 ` "meson test" very slow on Windows Johannes Sixt
2025-02-02 11:15 ` Patrick Steinhardt
2025-02-02 21:45 ` M Hickford
2025-02-02 23:13 ` brian m. carlson
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='CAGJzqsmmq1R9_q=p_AsuFMFr3UzyQ4H186CpfWTnCoAnHu_OXA@mail.gmail.com' \
--to=mirth.hickford@gmail.com \
--cc=git@vger.kernel.org \
--cc=ps@pks.im \
--cc=soekkle@freenet.de \
/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).