On 25. Jul 2019, at 19:38, Ludovic Courtès wrote:
> Robert Vollmert skribis:
>
The current status of the evaluation of wip-haskell-updates is quite
confusing. There are a number of jobs listed as “Scheduled” with a red
X mark at the front. Is this a bug?
>>>
>>> I think I found w
Hi,
Robert Vollmert skribis:
>>> The current status of the evaluation of wip-haskell-updates is quite
>>> confusing. There are a number of jobs listed as “Scheduled” with a red
>>> X mark at the front. Is this a bug?
>>
>> I think I found what causes this: Those jobs were actually in state
>> “
> On 22. Jul 2019, at 22:44, Robert Vollmert wrote:
>
>
>
>> On 22. Jul 2019, at 21:50, Robert Vollmert wrote:
>>
>> Hi Ricardo,
>>
>>> On 22. Jul 2019, at 21:01, Ricardo Wurmus wrote:
>>>
Now I was wondering how to get CI to test that.
>>>
>>> Adding branches is currently done ma
> On 22. Jul 2019, at 21:50, Robert Vollmert wrote:
>
> Hi Ricardo,
>
>> On 22. Jul 2019, at 21:01, Ricardo Wurmus wrote:
>>
>>> Now I was wondering how to get CI to test that.
>>
>> Adding branches is currently done manually. I’ll just update the
>> table of branches to build on ci.guix.
Hi Ricardo,
> On 22. Jul 2019, at 21:01, Ricardo Wurmus wrote:
>
>> Now I was wondering how to get CI to test that.
>
> Adding branches is currently done manually. I’ll just update the
> table of branches to build on ci.guix.gnu.org in a few minutes.
nice, thanks!
The current status of the e
Hi Robert,
> just pushed my first commit to the new branch wip-haskell-updates,
> yay!
Yay!
> Now I was wondering how to get CI to test that.
Adding branches is currently done manually. I’ll just update the
table of branches to build on ci.guix.gnu.org in a few minutes.
> (By the way there’
Hi all,
just pushed my first commit to the new branch wip-haskell-updates,
yay!
Now I was wondering how to get CI to test that. From a trip through
the sources, the following would appear to work:
In guix/gnu/ci.scm:
Define %haskell-packages, e.g. as all packages defined in
gnu/packages/hask
