git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: <rsbecker@nexbridge.com>
To: "'Ævar Arnfjörð Bjarmason'" <avarab@gmail.com>
Cc: <git@vger.kernel.org>, "'Jeff Hostetler'" <jeffhost@microsoft.com>
Subject: RE: [BUG} t2201.7+ Failure to Create Thread in 2.39.0-rc0
Date: Thu, 24 Nov 2022 17:22:16 -0500	[thread overview]
Message-ID: <011c01d90053$38e50900$aaaf1b00$@nexbridge.com> (raw)
In-Reply-To: <221124.86bkownhqd.gmgdl@evledraar.gmail.com>

On November 24, 2022 4:51 PM, Ævar Arnfjörð Bjarmason wrote:
>On Thu, Nov 24 2022, Ævar Arnfjörð Bjarmason wrote:
>
>> [CC-ing Jeff, this is from the "stopwatch timers" topic]
>>
>> On Thu, Nov 24 2022, rsbecker@nexbridge.com wrote:
>>
>>> While running t2201.7 (and subsequent) for 2.39.0-rc0, I hit a
>>> condition
>>> where:
>>
>> Don't you mean t0211-trace2-perf.sh?
>>
>>> <snip>
>>> + test_when_finished rm trace.perf actual test_config_global
>>> + trace2.perfBrief 1 pwd test_config_global trace2.perfTarget
>>> /home/ituglib/randall/jenkins/.jenkins/workspace/Git_Pipeline/t/trash
>>> directory.t0211-trace2-perf/trace.perf
>>> + test-tool trace2 101timer 5 10 3
>>> fatal: failed to create thread[0]
>>>
>>> was encountered, causing the test to fail. Pointers on resolving this
>>> would be helpful.
>>
>> Apparently we really could use a NO_PTHREADS=Y CI setup, because
>> that's all that's needed to reproduce this on linux & elsewhere.
>> Running the test with that:
>>
>> 	+ test-tool trace2 101timer 5 10 3
>> 	fatal: failed to create thread[0]
>> 	error: last command exited with $?=128
>>
>> For that all that's needed is this:
>>
>> 	diff --git a/t/t0211-trace2-perf.sh b/t/t0211-trace2-perf.sh
>> 	index 0b3436e8cac..cfba6861322 100755
>> 	--- a/t/t0211-trace2-perf.sh
>> 	+++ b/t/t0211-trace2-perf.sh
>> 	@@ -203,7 +203,7 @@ test_expect_success 'stopwatch timer test/test1' '
>> 	 	have_timer_event "main" "timer" "test" "test1" 5 actual
>> 	 '
>>
>> 	-test_expect_success 'stopwatch timer test/test2' '
>> 	+test_expect_success PTHREADS 'stopwatch timer test/test2' '
>> 	 	test_when_finished "rm trace.perf actual" &&
>> 	 	test_config_global trace2.perfBrief 1 &&
>> 	 	test_config_global trace2.perfTarget "$(pwd)/trace.perf" &&
>> 	@@ -249,7 +249,7 @@ test_expect_success 'global counter test/test1' '
>> 	 	have_counter_event "main" "counter" "test" "test1" 15 actual
>> 	 '
>>
>> 	-test_expect_success 'global counter test/test2' '
>> 	+test_expect_success PTHREADS 'global counter test/test2' '
>> 	 	test_when_finished "rm trace.perf actual" &&
>> 	 	test_config_global trace2.perfBrief 1 &&
>> 	 	test_config_global trace2.perfTarget "$(pwd)/trace.perf" &&
>>
>> I think that's the correct fix here, and it should go into rc1.
>
>I submitted a fix at
>https://lore.kernel.org/git/patch-1.1-f7f21c94a6c-20221124T214813Z-
>avarab@gmail.com/;
>but I see that since your message-id's contain "$" I got the In-Reply-To wrong,
>sorry :)

Thanks



      reply	other threads:[~2022-11-24 22:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-24 17:59 [BUG} t2201.7+ Failure to Create Thread in 2.39.0-rc0 rsbecker
2022-11-24 18:40 ` Ævar Arnfjörð Bjarmason
2022-11-24 19:18   ` rsbecker
2022-11-24 21:35     ` Ævar Arnfjörð Bjarmason
2022-11-24 21:51   ` Ævar Arnfjörð Bjarmason
2022-11-24 22:22     ` rsbecker [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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='011c01d90053$38e50900$aaaf1b00$@nexbridge.com' \
    --to=rsbecker@nexbridge.com \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jeffhost@microsoft.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).