public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "samuel.thibault@ens-lyon.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug hurd/30342] New: test-lfs puts the box on its knees
Date: Thu, 13 Apr 2023 00:02:11 +0000 [thread overview]
Message-ID: <bug-30342-131@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=30342
Bug ID: 30342
Summary: test-lfs puts the box on its knees
Product: glibc
Version: 2.38
Status: NEW
Severity: normal
Priority: P2
Component: hurd
Assignee: unassigned at sourceware dot org
Reporter: samuel.thibault@ens-lyon.org
CC: samuel.thibault@ens-lyon.org, tschwinge at sourceware dot org
Target Milestone: ---
The test-lfs test seems to be making the file server generate GiBs of data
instead of sparse files, the putting build box on its knees. This is most
probably missing support for large sparse files in the server, but recording it
here before marking as unsupported.
--
You are receiving this mail because:
You are on the CC list for the bug.
reply other threads:[~2023-04-13 0:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-30342-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: 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 read-only IMAP folder(s) and NNTP newsgroup(s).