GNU bug report logs -
#65391
People need to report failing builds even though we have ci.guix.gnu.org for that
Previous Next
Full log
View this message in rfc822 format
Simon Tournier <zimon.toutoune <at> gmail.com> writes:
> Hi,
>
> On Wed, 23 Aug 2023 at 01:45, Csepp <raingloom <at> riseup.net> wrote:
>
>> One possible improvement I have been thinking about is making it easy
>> for users to filter CI output to the packages in their profile closure,
>> so for example they would get advance notice of any broken packages
>> *before* attempting to install them.
>> Teams could also have their own filters.
>
> Maybe I am missing what you would like, from my understanding, that’s
> already possible using time-machine and weather. For example,
>
> guix time-machine -- weather -m manifest.scm
>
> allow to know the status of the last commit. What is missing is a clear
> return code for chaining. For instance, see this proposal:
>
> subject: guix weather exit status?
> from: Leo Famulari <leo <at> famulari.name>
> date: Thu, 08 Jul 2021 16:35:03 -0400
> message-id: id:YOdhd7FfMOvKjTQe <at> jasmine.lan
> https://yhetil.org/guix/YOdhd7FfMOvKjTQe <at> jasmine.lan
>
> However, I agree that the next step (find the log of the broken package)
> for teams is a bit convoluted.
>
> Cheers,
> simon
Thanks, I was not aware of this solution, but it also kind of isn't a
complete solution.
A pull is a quite costly operation, why should I have to perform one on
my netbook when what I'm trying to find out is which commit is actually
worth pulling to?
This bug report was last modified 1 year and 191 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.