From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: "Gábor Boskovits" <boskovits@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: I don't understand the Curiass WebUI
Date: Wed, 2 Oct 2019 15:24:26 +0200 [thread overview]
Message-ID: <8a4235c3-04ae-d3f9-8aaf-eb5ca54489e6@crazy-compilers.com> (raw)
In-Reply-To: <CAE4v=pjZDC3oxFQDm6eESSvwxhaYKV_hPyFNik9b8--2A=V6Fg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1158 bytes --]
Hello,
Am 02.10.19 um 14:32 schrieb Gábor Boskovits:
>
> You are looking for guix-master. The interface shows for a given
> evalution only
> the packages that were scheduled because of the difference between the
> evaluation
> and the previous one.
IC. I assume old hydra was not able to evaluate that fast, thus the
there have been more packages for each evaluation.
Now e.g. ci.guix.gnu.org/eval/7761 contains the rebuild of exactly one
package (next) - which is hard to spot sine it is buried by many "image"
builds.
> I believe it would make sense to have an aggregate package view,
> showing the current status of the packages, and the evaluation when
> they were last attempted,
> and the result of that attempt. Wdyt?
This would be helpful, esp. if it is placed somewhat prominently.
Another possibility would be improve the search-filters.
FWIW: Check when a package has been build the last time (for some
specific platform).
--
Regards
Hartmut Goebel
| Hartmut Goebel | h.goebel@crazy-compilers.com |
| www.crazy-compilers.com | compilers which you thought are impossible |
[-- Attachment #2: Type: text/html, Size: 2487 bytes --]
next prev parent reply other threads:[~2019-10-02 13:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-02 12:10 I don't understand the Curiass WebUI Hartmut Goebel
2019-10-02 12:32 ` Gábor Boskovits
2019-10-02 13:24 ` Hartmut Goebel [this message]
2019-10-04 21:37 ` Björn Höfling
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8a4235c3-04ae-d3f9-8aaf-eb5ca54489e6@crazy-compilers.com \
--to=h.goebel@crazy-compilers.com \
--cc=boskovits@gmail.com \
--cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).