public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pianweiqu1 at 126 dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug string/29995] New: Make check failed on glibc@2.36 and master:string/tst-strerror,string/tst-strsignal,stdlib/isomac Date: Fri, 13 Jan 2023 03:47:41 +0000 [thread overview] Message-ID: <bug-29995-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=29995 Bug ID: 29995 Summary: Make check failed on glibc at 2 dot 36 and master:string/tst-strerror,string/tst-strsignal,stdlib /isomac Product: glibc Version: 2.36 Status: UNCONFIRMED Severity: normal Priority: P2 Component: string Assignee: unassigned at sourceware dot org Reporter: pianweiqu1 at 126 dot com Target Milestone: --- Make check failed on glibc@2.36 and master: os:centos platform:aarch64/x86_64 LC_ALL=C FAIL: misc/tst-mount-consts UNSUPPORTED: misc/tst-ntp_adjtime … … FAIL: stdlib/isomac UNSUPPORTED: stdlib/tst-quick_exit UNSUPPORTED: stdlib/tst-secure-getenv UNSUPPORTED: stdlib/tst-thread-quick_exit FAIL: string/tst-strerror FAIL: string/tst-strsignal UNSUPPORTED: time/tst-clock_settime UNSUPPORTED: time/tst-settimeofday Summary of test results: 4 FAIL 4545 PASS 48 UNSUPPORTED 16 XFAIL 2 XPASS -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2023-01-13 3:47 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-13 3:47 pianweiqu1 at 126 dot com [this message] 2023-01-13 10:26 ` [Bug string/29995] " schwab@linux-m68k.org 2023-01-18 3:47 ` pianweiqu1 at 126 dot com 2023-01-18 3:48 ` pianweiqu1 at 126 dot com 2023-01-18 3:50 ` pianweiqu1 at 126 dot com 2023-02-13 1:24 ` pianweiqu1 at 126 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-29995-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).