From: "H.J. Lu" <hjl.tools@gmail.com>
To: "Frank Ch. Eigler" <fche@elastic.org>
Cc: overseers@gcc.gnu.org
Subject: Re: GCC bugzilla is broken
Date: Sun, 16 Aug 2015 13:19:00 -0000 [thread overview]
Message-ID: <CAMe9rOohqmk9twqGH8q40EbnD=Vq3gY8SzwmTOjj06nVw6-VXA@mail.gmail.com> (raw)
In-Reply-To: <20150816130656.GK72703@elastic.org>
On Sun, Aug 16, 2015 at 6:06 AM, Frank Ch. Eigler <fche@elastic.org> wrote:
> Hi -
>
>> Visiting any bug report, like
>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66691
>> leads to
>> An unexpected error occurred. [...]
>
> This was due to a fillup of the root filesystem; fixed now.
No completely. When I tried to upload an attachment, I got
Software error:
DBD::mysql::db do failed: Table './bugs/bugs_fulltext' is marked as
crashed and last (automatic?) repair failed [for Statement "UPDATE
bugs_fulltext SET comments = ?, comments_noprivate = ? WHERE bug_id =
?"] at Bugzilla/Bug.pm line 1248.
Bugzilla::Bug::_sync_fulltext(Bugzilla::Bug=HASH(0x3e08288),
"update_short_desc", undef, "update_comments", ARRAY(0x11bca98))
called at Bugzilla/Bug.pm line 1180
Bugzilla::Bug::update(Bugzilla::Bug=HASH(0x3e08288), "2015-08-16
13:18:01") called at /www/gcc/bugzilla/attachment.cgi line 556
main::insert() called at /www/gcc/bugzilla/attachment.cgi line 85
For help, please send mail to the webmaster
(sourcemaster@sourceware.org), giving this error message and the time
and date of the error.
--
H.J.
next prev parent reply other threads:[~2015-08-16 13:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-16 13:02 H.J. Lu
2015-08-16 13:07 ` Frank Ch. Eigler
2015-08-16 13:19 ` H.J. Lu [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-09-27 15:29 gcc " Andrew Haley
2010-09-27 15:38 ` Daniel Berlin
2010-09-27 15:42 ` Frédéric Buclin
2010-09-27 16:44 ` Christopher Faylor
2010-09-27 17:45 ` Christopher Faylor
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='CAMe9rOohqmk9twqGH8q40EbnD=Vq3gY8SzwmTOjj06nVw6-VXA@mail.gmail.com' \
--to=hjl.tools@gmail.com \
--cc=fche@elastic.org \
--cc=overseers@gcc.gnu.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).