From: "宋文武 via Bug reports for GNU Guix" <bug-guix@gnu.org>
To: 65391@debbugs.gnu.org
Cc: maxim.cournoyer@gmail.com
Subject: bug#65391: [Cuirass] feature requests for dashboard
Date: Sun, 27 Aug 2023 16:16:29 +0800 [thread overview]
Message-ID: <877cpgc336.fsf_-_@envs.net> (raw)
In-Reply-To: <87sf85i289.fsf@gmail.com> (Maxim Cournoyer's message of "Sat, 26 Aug 2023 23:38:30 -0400")
Hello, I think the current CI dashboard (eg: https://ci.guix.gnu.org/eval/693369/dashboard)
is a little inconvenient to use, and I'd like it have:
1. different colors for build failures (status=1) and dependencies
failures (status=2), and other type failures. Maybe yellow for
dependencies failures, and grey for other.
2. more search options in addition to job name, eg:
status:failed
status:failed-dependency
status:canceled
team:python
also a help like in mumi https://issues.guix.gnu.org/help#search for
those options.
3. for a failed build, show a link to its bug report on
issues.guix.gnu.org if one existed.
eg, for: https://ci.guix.gnu.org/build/1170869/details
add a Issue row with link to https://issues.guix.gnu.org/65392
so we can know this build failure is known.
Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
>> I found the dashboard inconvenient to use, it show failures for both
>> builds and dependencies in the same red color, and can't be searched.
>> What I usually do is:
>>
>> 1. download the job status json with:
>> wget -O jobs.json 'https://ci.guix.gnu.org/api/jobs?evaluation=692229&system=x86_64-linux'
>>
>> 2. use jq to show package names with build failures:
>> cat jobs.json | jq '. | map(select(.status == 1)) | .[].name' -r
>>
>> 3. select interested one to investigate (if doing merge, diff the failures from
>> working branch with master).
>
> Maybe we should open Cuirass feature requests on our bug tracker to
> remember what would be valuable to implement.
Okay, I'll open one here.
next prev parent reply other threads:[~2023-08-27 8:17 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-19 23:53 bug#65391: People need to report failing builds even though we have ci.guix.gnu.org for that Maxime Devos
2023-08-22 23:45 ` Csepp
2023-08-24 9:57 ` Simon Tournier
2023-08-24 17:23 ` Csepp
2023-08-24 14:52 ` Maxime Devos
2023-08-24 17:27 ` Csepp
2023-08-29 22:52 ` Maxime Devos
2023-08-30 2:36 ` Maxim Cournoyer
2023-08-24 15:02 ` Maxime Devos
2023-08-24 17:38 ` Csepp
2023-08-27 1:13 ` 宋文武
2023-08-27 3:38 ` Maxim Cournoyer
2023-08-27 8:16 ` 宋文武 via Bug reports for GNU Guix [this message]
2023-08-27 3:39 ` Maxim Cournoyer
2023-08-27 4:30 ` Bruno Victal
2023-08-27 15:07 ` Giovanni Biscuolo
2023-08-27 16:24 ` bug#65391: People need to report failing builds even Andy Tai
2023-08-27 21:26 ` Andy Tai
[not found] ` <handler.65391.B.169248925726403.ack@debbugs.gnu.org>
2023-08-29 14:03 ` bug#65391: Acknowledgement (People need to report failing builds even though we have ci.guix.gnu.org for that) Maxime Devos
2023-08-29 14:45 ` Maxim Cournoyer
2023-08-29 22:44 ` Maxime Devos
2023-08-30 2:28 ` Maxim Cournoyer
2023-08-30 10:39 ` Dr. Arne Babenhauserheide
2023-08-30 19:12 ` Maxim Cournoyer
2023-09-07 11:53 ` Simon Tournier
2023-09-11 8:30 ` Dr. Arne Babenhauserheide
2023-09-11 14:00 ` Simon Tournier
2023-09-11 23:12 ` Dr. Arne Babenhauserheide
2023-09-12 0:39 ` Simon Tournier
2023-08-30 11:50 ` Maxime Devos
2023-09-07 11:32 ` Simon Tournier
2023-09-11 7:28 ` bug#65391: People need to report failing builds even though we have ci.guix.gnu.org for that Csepp
2023-09-11 7:58 ` Simon Tournier
2023-09-11 21:52 ` Csepp
2023-09-12 18:43 ` bug#65391: Acknowledgement (People need to report failing builds even though we have ci.guix.gnu.org for that) Maxime Devos
2023-08-30 10:29 ` 宋文武 via Bug reports for GNU Guix
2024-02-14 9:13 ` bug#65391: Close Andreas Enge
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=877cpgc336.fsf_-_@envs.net \
--to=bug-guix@gnu.org \
--cc=65391@debbugs.gnu.org \
--cc=iyzsong@envs.net \
--cc=maxim.cournoyer@gmail.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.