From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from eggs.gnu.org (eggs.gnu.org [IPv6:2001:470:142:3::10]) by sourceware.org (Postfix) with ESMTPS id 70D0A3858D33 for ; Wed, 12 Apr 2023 09:00:28 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 70D0A3858D33 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=gnu.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=gnu.org Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pmWL5-0001Od-O3; Wed, 12 Apr 2023 05:00:27 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=In-Reply-To:MIME-Version:References:Subject:To:From: Date; bh=RRi+fmIMViLdo+FK63YTbEx+G1Raor+FlcgsdtAd0JI=; b=DqUhhjDghOUoCpll0xzY 0C92TubrB3sVbTkJSXIVMgcARyBhIckUXgVM+cnUB0SuBLX5IIiIxGZ5NriXRuiGHTEQFKcPN8pfC JgHtVV6sQMnJNo+X/0FwgPc4cpOz9k+6dkyG4XpDJrE9s3Ca4JQA6tqY50oR5YCN/5PqxsTO8WpGs P/XoEq6z0SJJoo19iDTOCqBlF5a2kYlkwoxDStu3Ev2Wa8NVP1hrGWZOR5nfjVx91L2RkkdDeADDA 5gdnQvgM2vLpdzRg0fqFhWGpy9/T3+BJIe+gjk9JAxZvsz9qKQ766Xn6DF9Bnp3mtXiaLsca8HD7f 3R6qLFZ4S/tUbw==; Received: from nat-inria-interne-52-gw-01-bso.bordeaux.inria.fr ([194.199.1.52] helo=begin) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pmWL5-0000sF-Bq; Wed, 12 Apr 2023 05:00:27 -0400 Received: from samy by begin with local (Exim 4.96) (envelope-from ) id 1pmWL3-006WLb-0K; Wed, 12 Apr 2023 11:00:25 +0200 Date: Wed, 12 Apr 2023 11:00:25 +0200 From: Samuel Thibault To: Sergey Bugaev Cc: libc-alpha@sourceware.org, bug-hurd@gnu.org Subject: Re: [RFC PATCH glibc 24/34] hurd: Only check for TLS initialization inside rtld or in static builds Message-ID: <20230412090025.rjqbtx2zakk5r6yx@begin> Mail-Followup-To: Sergey Bugaev , libc-alpha@sourceware.org, bug-hurd@gnu.org References: <20230319151017.531737-1-bugaevc@gmail.com> <20230319151017.531737-25-bugaevc@gmail.com> <20230411185705.22jygrepjq4mhbvk@begin> <20230411212346.ligmclr5ph7gowl5@begin> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: I am not organized User-Agent: NeoMutt/20170609 (1.8.3) X-Spam-Status: No, score=-6.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_PASS,SPF_PASS,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: Sergey Bugaev, le mer. 12 avril 2023 11:36:58 +0300, a ecrit: > Alright, this went much as expected. First it took an eternity to > compile (SMP support can't come soon enough), and second, the testuite > has brought the system into a bad state and didn't complete. In > particular: it managed to terminate my SSH session several times (I > don't know how), and eventually it ran into that networking stack > deadlock (the only way out of which seems to be reboot-hurd on the > console). So I still can not run the testsuite on my end. Was that tst-spawn6? We'd probably have to disable that as well, you can just add tests-unsupported += tst-spawn6 to sysdeps/mach/hurd/Makefile Possibly also test-lfs: tests-unsupported += test-lfs > But the tests that did run seem to mostly have worked. There were some > failures here and there (I don't know which ones are expected) You can run on master to get the list of current expected failures. > Could you please point me to a specific test case Actually all cases that actually execute something, fail. So for instance the very first, csu/test-as-const-rtld-sizes > (and not just "run the whole thing") that started failing because of > this change, and teach me how to run just that one? I have read [0], > but that says, "To test just one test you have to have already run the > entire testsuite", which is a non-starter. You can use ./testrun.sh csu/test-as-const-rtld-sizes > Would it have been easy for me to run the full test suite, I would > surely do that before submitting any patches. But it's not. Then it's simple: we have to fix that first. Samuel