KernelCI discussions
 help / color / mirror / Atom feed
From: "Nikolai Kondrashov" <spbnick@gmail.com>
To: kernelci@groups.io, dvyukov@google.com
Cc: syzkaller <syzkaller@googlegroups.com>,
	Taras Madan <tarasmadan@google.com>
Subject: Re: Resource not found (resource=kernelci_new)
Date: Fri, 7 Jan 2022 18:25:07 +0200	[thread overview]
Message-ID: <c0585fe0-6502-8c7c-45ad-e6f2e6a99383@gmail.com> (raw)
In-Reply-To: <CACT4Y+ZtsKROJu13VSZcJDCb=rHbF7oh09LVUe3NKGDO3X4L0g@mail.gmail.com>

Hi Dmitry,

This is due to the rename of the submission topic I announced in the "#KCIDB 
v9 release" thread. You were in the recipients, but perhaps the address was 
wrong, or you didn't get it for some other reason?

It should work again, if you switch to using "kcidb_new" topic, instead of 
"kernelci_new".

Thank you.
Nick

On 1/7/22 17:38, Dmitry Vyukov via groups.io wrote:
> Hi,
> 
> We've started getting the following errors on syzbot while trying to
> submit KCIDB reports:
> 
> Jan  5 12:09:00: 200 GET /kcidb_poll "kcidb: upstream failed: rpc
> error: code = NotFound desc = Resource not found
> (resource=kernelci_new)."
> Jan  5 12:14:00: 200 GET /kcidb_poll "kcidb: upstream failed: rpc
> error: code = NotFound desc = Resource not found
> (resource=kernelci_new)."
> Jan  5 12:19:00: 200 GET /kcidb_poll "kcidb: upstream failed: rpc
> error: code = NotFound desc = Resource not found
> (resource=kernelci_new)."
> 
> There may be something changed/broken on our side. But I don't see
> anything obvious yet. So wanted to ask if it rings any bells on your
> end?
> 
> Thanks
> 
> 
> 
> 
> 


  reply	other threads:[~2022-01-07 16:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-07 15:38 Resource not found (resource=kernelci_new) Dmitry Vyukov
2022-01-07 16:25 ` Nikolai Kondrashov [this message]
2022-01-07 16:31   ` Dmitry Vyukov

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=c0585fe0-6502-8c7c-45ad-e6f2e6a99383@gmail.com \
    --to=spbnick@gmail.com \
    --cc=dvyukov@google.com \
    --cc=kernelci@groups.io \
    --cc=syzkaller@googlegroups.com \
    --cc=tarasmadan@google.com \
    /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