public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug dynamic-link/28550] New: FAIL: tst-dso-ordering9_112-ecbda(GLIBC_TUNABLES=glibc.rtld.dynamic_sort=1) execution test Date: Fri, 05 Nov 2021 13:34:56 +0000 [thread overview] Message-ID: <bug-28550-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=28550 Bug ID: 28550 Summary: FAIL: tst-dso-ordering9_112-ecbda(GLIBC_TUNABLES=glibc.rtld. dynamic_sort=1) execution test Product: glibc Version: 2.35 Status: NEW Severity: normal Priority: P2 Component: dynamic-link Assignee: unassigned at sourceware dot org Reporter: hjl.tools at gmail dot com CC: cltang at codesourcery dot com Target Milestone: --- The new dso-sort-tests-1 fails for different reasons at random on many-core machine with load. elf/Makefile has # DSO sorting tests: # The dso-ordering-test.py script generates testcase source files in $(objpfx), # creating a $(objpfx)<testcase-name>-dir for each testcase, and creates a # Makefile fragment to be included. define include_dsosort_tests $(objpfx)$(1).generated-makefile: $(1) $(PYTHON) $(..)scripts/dso-ordering-test.py \ --description-file $$< --objpfx $(objpfx) --output-makefile $$@ include $(objpfx)$(1).generated-makefile endef # Generate from each testcase description file ifeq (yes,$(have-tunables)) $(eval $(call include_dsosort_tests,dso-sort-tests-1.def)) $(eval $(call include_dsosort_tests,dso-sort-tests-2.def)) endif I don't think it works well with parallel build on many-core machines. I think it should be changed to use configure.ac or Makeconfig to generate these makefile fragments. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2021-11-05 13:34 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-05 13:34 hjl.tools at gmail dot com [this message] 2021-11-06 14:54 ` [Bug dynamic-link/28550] " hjl.tools at gmail dot com 2021-11-06 18:10 ` hjl.tools at gmail dot com 2021-11-06 23:16 ` hjl.tools at gmail dot com 2021-11-15 19:54 ` cvs-commit at gcc dot gnu.org 2021-11-16 13:18 ` cvs-commit at gcc dot gnu.org 2021-11-16 13:19 ` hjl.tools at gmail dot com
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=bug-28550-131@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.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: linkBe 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 read-only IMAP folder(s) and NNTP newsgroup(s).