Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Peres, Martin" <martin.peres@intel.com>
To: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [CI] Pre-merge testing disabled
Date: Wed, 17 Jun 2020 08:29:10 +0000	[thread overview]
Message-ID: <91072193e4654296924cd9ca13463da8@intel.com> (raw)
In-Reply-To: c80cb85e77c74b949ab75778b330494b@intel.com

[-- Attachment #1: Type: text/plain, Size: 684 bytes --]

On 2020-06-16 12:37, Peres, Martin wrote:
> Hello world,
> 
> Due to changes in our global data policy rules, the bucket used to store
> the CI results became private, which prevents us from providing any
> testing result.
> 
> We have received a notice on Sunday about this change, notified them on
> Monday that we wanted to keep our storage public and ended up on Tuesday
> with a private bucket.
> 
> We are working as fast as possible to address this, but we cannot give
> any ETA. We'll be updating you in this thread.
> 
> Sorry for the inconvenience,
> Martin

Thanks to Tomi Sarvela for his efforts, it's back!

Sorry again for the inconvenience!
Martin

[-- Attachment #2: pEpkey.asc --]
[-- Type: application/pgp-keys, Size: 1765 bytes --]

[-- Attachment #3: Type: text/plain, Size: 160 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2020-06-17  8:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-16  9:37 [Intel-gfx] [CI] Pre-merge testing disabled Peres, Martin
2020-06-17  8:29 ` Peres, Martin [this message]

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=91072193e4654296924cd9ca13463da8@intel.com \
    --to=martin.peres@intel.com \
    --cc=intel-gfx@lists.freedesktop.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