public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Sunil Pandey <skpgkp2@gmail.com>
To: overseers@sourceware.org
Subject: account locked.
Date: Sun, 7 Jun 2020 14:10:10 -0700	[thread overview]
Message-ID: <CAMAf5_f1j+DM6RjhE7oGnYYrrOdotzXcwLRuYgOMxqh8jVOkRA@mail.gmail.com> (raw)

Hi,

My account(skpgkp2@gmail.com) got locked while updating the bug report. I
believe my account should be restored. I don't see anything inappropriate
about updating a bug report with the following status update. It got locked
while updating this bug.

https://sourceware.org/bugzilla/show_bug.cgi?id=25933

Can you please take a look and let me know which word I shouldn't use in
future to avoid this problem.

Here is the exact text of my comment.

[[I ran "make one" and got the following result.

UNSUPPORTED: elf/tst-audit10
UNSUPPORTED: elf/tst-avx512
UNSUPPORTED: elf/tst-env-setuid
UNSUPPORTED: elf/tst-env-setuid-tunables
XPASS: elf/tst-protected1a
XPASS: elf/tst-protected1b
UNSUPPORTED: math/test-double-libmvec-sincos-avx512
UNSUPPORTED: math/test-float-libmvec-sincosf-avx512
UNSUPPORTED: misc/tst-pkey
UNSUPPORTED: nptl/test-cond-printers
UNSUPPORTED: nptl/test-condattr-printers
UNSUPPORTED: nptl/test-mutex-printers
UNSUPPORTED: nptl/test-mutexattr-printers
UNSUPPORTED: nptl/test-rwlock-printers
UNSUPPORTED: nptl/test-rwlockattr-printers
FAIL: wcsmbs/test-wcsncmp
Summary of test results:
      1 FAIL
   4229 PASS
     13 UNSUPPORTED
     17 XFAIL
      2 XPASS

]]

             reply	other threads:[~2020-06-07 21:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-07 21:10 Sunil Pandey [this message]
2020-06-07 21:32 ` Mark Wielaard
  -- strict thread matches above, loose matches on Subject: below --
2019-11-05 18:53 Reinoud Koornstra
2019-11-05 18:59 ` Frank Ch. Eigler
2019-11-05 20:56   ` Reinoud Koornstra
2019-11-05 20:57     ` Frank Ch. Eigler

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=CAMAf5_f1j+DM6RjhE7oGnYYrrOdotzXcwLRuYgOMxqh8jVOkRA@mail.gmail.com \
    --to=skpgkp2@gmail.com \
    --cc=overseers@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).