[Nix-dev] Haskell build failures

Mateusz Kowalczyk fuuzetsu at fuuzetsu.co.uk
Thu Aug 21 07:19:34 CEST 2014


On 08/21/2014 05:46 AM, Raahul Kumar wrote:
> How? Amazing well done! But seriously how was this achieved?
> 
> 
> On Thu, Aug 21, 2014 at 4:45 AM, Luca Bruno <lethalman88 at gmail.com> wrote:
> 
>> Wow, awesome.
>>
>>
>> On Wed, Aug 20, 2014 at 8:33 PM, Peter Simons <simons at cryp.to> wrote:
>>
>>> On Linux/x86_64, zero Haskell builds fail:
>>>
>>>   http://hydra.cryp.to/jobset/nixpkgs/haskell-updates
>>>
>>> Let's hope that lasts. :-)
>>>
>>> Best regards,
>>> Peter
>>>

It was achieved by marking broken things as broken so that they don't
come up as failures on Hydra all the time. Once the package is fixed
(upstream or otherwise) it can be built again and we have an extra
package building.

The approach of marking stuff as broken allows one to see much better
which packages actually change build status. Users also get a message if
they try to compile a package marked as broken rather than have them try
to compile and fail which was horrible user experience.

-- 
Mateusz K.


More information about the nix-dev mailing list