From: "Laszlo Ersek" <lersek@redhat.com>
To: "Kinney, Michael D" <michael.d.kinney@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>,
Sean Brogan <sean.brogan@microsoft.com>,
Bret Barkelew <Bret.Barkelew@microsoft.com>,
"Gao, Liming" <liming.gao@intel.com>
Subject: Re: [edk2-devel] EDK II Maintainers - EDK II CI is now active on edk2/master
Date: Tue, 7 Jan 2020 10:00:19 +0100 [thread overview]
Message-ID: <69b8aeff-9af0-6ff6-b806-f7ac0d64f76a@redhat.com> (raw)
In-Reply-To: <E92EE9817A31E24EB0585FDF735412F5B9E58033@ORSMSX113.amr.corp.intel.com>
Hello Mike,
On 01/06/20 19:17, Kinney, Michael D wrote:
> Laszlo,
>
> Sorry for the delay in getting to these PactchCheck.py updates.
> I know it is frustrating to be blocked by these types of issues.
> I try to look at 2406 tomorrow.
Thanks!
> I think the manual override is
> potentially more complex to implement than the requested changed
> to PatchCheck.py.
OK.
>
> You were on the correct link. If you clicked one more level on
> "Bash exited with code '255'" link on that web page, it takes you
> to the patch check log that shows 3 errors for commit message
> subject lines being too long.
>
> https://dev.azure.com/tianocore/edk2-ci/_build/results?buildId=3459&view=logs&j=12f1170f-54f2-53f3-20dd-22fc7dff55f9&t=9c939e41-62c2-5605-5e05-fc3554afc9f5&l=149
Thanks for this info as well. I have two comments, one specific and one
general ("rambling").
(1) The specific comment: the above link does not work for me. I get:
An unexpected error has occurred within this region of the page.
You can try reloading this component or refreshing the entire page.
with two buttons:
[Refresh page] [Reload component]
Neither helps -- the result is the same. Then, if I click "Show more
info", I get:
Error: 'block' member of ScrollIntoViewOptions 'center' is not a valid
value for enumeration ScrollLogicalPosition.
Stack
in i in t in div in t in li ...
The result is the same if I start with the link from yesterday:
https://dev.azure.com/tianocore/11ea4a10-ac9f-4e5f-8b13-7def1f19d478/_build/results?buildId=3456
and then indeed click the "Bash exited with code '255'" link.
Worse, even the github.com link that I posted myself yesterday:
https://github.com/tianocore/edk2/pull/272/checks?check_run_id=375969977
has stopped working now. Apparently failed CI runs are superseded by
successful ones, and we can no longer refer to historic failures. This
is not very helpful (in particular for the CI system's developers, I'd
think!).
(2) The general comment. In the old [X]HTML days, a button looked like a
button, and a link looked like a link. Today, on the Modern Web (TM),
visual cues as to whether a UI element is "active" or not, are
unpredictable. To me anyway. There are too many colors, and the active
elements frequently lack a consistent trait -- even within a single web
page -- that advertises "I'm active, click me", without the user
hovering over them with the mouse pointer.
My question here is whether this is
- just me,
- my background (~ textual terminals),
- my generation (Gen X, let's say).
I feel like UI design has fallen off a cliff in recent years.
(Bonus offense: text that cannot be selected for copy & paste. For
example, I cannot highlight the "Bash exited with code '255'" link, for
copying that caption into this email. I have to re-type it manually.)
Thanks
Laszlo
next prev parent reply other threads:[~2020-01-07 9:00 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-12 2:55 EDK II Maintainers - EDK II CI is now active on edk2/master Michael D Kinney
2019-11-12 8:56 ` [edk2-devel] " Laszlo Ersek
2019-11-12 19:50 ` Michael D Kinney
2019-11-12 19:52 ` Michael D Kinney
2019-11-13 7:56 ` Laszlo Ersek
2019-11-13 8:57 ` Laszlo Ersek
2019-11-13 16:23 ` Michael D Kinney
2019-11-13 17:03 ` Laszlo Ersek
2019-11-26 8:23 ` Laszlo Ersek
2019-11-27 19:03 ` Michael D Kinney
2019-11-28 12:00 ` Laszlo Ersek
2019-12-02 19:55 ` Michael D Kinney
2019-12-03 8:56 ` Laszlo Ersek
2019-12-03 17:07 ` Michael D Kinney
2019-12-03 20:39 ` Laszlo Ersek
2019-12-06 11:02 ` Laszlo Ersek
2019-12-06 11:07 ` Laszlo Ersek
2020-01-02 14:42 ` Philippe Mathieu-Daudé
2020-01-02 18:36 ` Michael D Kinney
2020-01-06 14:58 ` Philippe Mathieu-Daudé
2020-01-03 13:29 ` Laszlo Ersek
2020-01-06 17:29 ` Laszlo Ersek
2020-01-06 18:17 ` Michael D Kinney
2020-01-07 9:00 ` Laszlo Ersek [this message]
2020-01-09 21:30 ` Laszlo Ersek
2020-01-09 21:37 ` Michael D Kinney
2020-01-10 10:51 ` Laszlo Ersek
2020-03-08 11:12 ` Laszlo Ersek
-- strict thread matches above, loose matches on Subject: below --
2020-03-08 19:21 Sean
2020-03-08 19:53 ` Michael D Kinney
2020-03-09 19:29 ` Laszlo Ersek
2020-03-09 19:32 ` Laszlo Ersek
2020-03-09 22:00 ` Michael D Kinney
2020-03-09 19:37 ` Laszlo Ersek
2020-03-09 20:06 ` Laszlo Ersek
2020-03-09 21:44 ` Michael D Kinney
2020-03-10 7:53 ` Laszlo Ersek
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-list 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=69b8aeff-9af0-6ff6-b806-f7ac0d64f76a@redhat.com \
--to=devel@edk2.groups.io \
/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