qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Richard Henderson <richard.henderson@linaro.org>,
	"Daniel P. Berrange" <berrange@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: gitlab/cirrus auth token failure
Date: Sun, 24 Oct 2021 09:42:43 +0200	[thread overview]
Message-ID: <f80220c1-84cd-e9c1-9542-40f4ea9aa419@redhat.com> (raw)
In-Reply-To: <8257c433-f8fb-7766-dec3-a220e9bee84b@linaro.org>

On 22/10/21 20:31, Richard Henderson wrote:
> Hi Daniel, you win the cookie because you committed cirrus.yml.
> 
> I should have reported this before the weekend, but at some point this 
> week the auth tokens expired(?).  All of the cirrus-run tests are now 
> failing:
> 
> cirrus_run.api.CirrusAPIError: API returned 1 error(s):
> [ { 'extensions': {'classification': 'DataFetchingException'},
>      'locations': [{'column': 13, 'line': 5}],
>      'message': 'Exception while fetching data (/createBuild) : '
>                 'AccessTokenAuthorization(token=[MASKED]) '
>                 "doesn't have permissions to create builds for "
>                 '5748266831446016!',
>      'path': ['createBuild']}]

It seems to have fixed itself for kvm-unit-tests, so maybe it was just a 
temporary issue within cirrus itself?

Paolo



  reply	other threads:[~2021-10-24  7:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-22 18:31 gitlab/cirrus auth token failure Richard Henderson
2021-10-24  7:42 ` Paolo Bonzini [this message]
2021-10-25  1:15   ` Richard Henderson
2021-10-25  8:17     ` Daniel P. Berrangé
2021-10-25 12:39       ` Thomas Huth

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=f80220c1-84cd-e9c1-9542-40f4ea9aa419@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=berrange@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.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 NNTP newsgroup(s).