From: "Peres, Martin" <martin.peres@intel.com>
To: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: [Intel-gfx] Connectivity issue to the CI system
Date: Mon, 29 Jun 2020 07:47:04 +0000 [thread overview]
Message-ID: <9114b53c837547c39a770b18002c7163@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 540 bytes --]
Hi everyone,
We have been experiencing connectivity issue for the past week to the CI
system which led to abnormal CI latencies:
https://intel-gfx-ci.01.org/latency.html?project=igt&test=Fi.CI.IGT
The issue has been under investigation, but unfortunately we do not know
when this issue will get resolved. It however got worse over the weekend
to the point that the CI system is completely unavailable.
Sorry about the issue, I will keep you updated as information becomes
available to me.
Martin, on behalf of the CI team
[-- Attachment #2: pEpkey.asc --]
[-- Type: application/pgp-keys, Size: 1774 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-29 7:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=9114b53c837547c39a770b18002c7163@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