Rare project developers

[Alexander Gall <>]

Hi

On Fri, 13 May 2022 08:50:31 +0200, mc36 <> said:

> i personally would prefer to keep running the bumpers directly on the 
> weekends to see the outcome...
> imho bumping freerouter should not break anything, but bumping rare 
> could... so instead of the pr
> model, could you please configure hydra to send an email to one of
> the lists if a build fails?

Notifications should now be sent to rare-dev. I hope this works, never
used that option before :)

There is also an API call that you could use to check:

curl -s -H 'Accept: application/json' 
'http://hydra.nix.net.switch.ch:3000/api/jobsets?project=RARE-OS' | jq '.[] | 
select (.name=="development").nrfailed'

This prints the number of "evaluations" (components of a build) that
have failed to build, i.e. that should be 0 for a successful
build. That's just the current status, though. To make this reliable
would probably require some more API calls.  But if the email method
is good enough, I would leave it at that.

-- 
Alex

> then i would be able to notice and act accordingly.... (for example revert 
> if i've no idea at all:)
> thanks,
> cs


> On 5/12/22 11:26, Alexander Gall wrote:
>> Hi csaba
>> 
>> As you may have noticed, your recent commits broke the RARE builds:
>> http://hydra.nix.net.switch.ch/jobset/RARE-OS/development
>> 
>> Two things are broken right now:
>> 
>> * Missing yappi Python module in the build environment
>> 
>> * The BNG profile fails to compile with 9.7.1
>> 
>> I will fix both but we should try to avoid this situation in view of
>> the tna-install-latest and tna-install-experimental features which
>> inherit these failures.  I suggest that we start using PRs for the
>> RARE-NIX repo so I can make sure that the builds won't fail. It will
>> usually take a few days for me to process the PRs since I'm not
>> working on the project full-time :)
>> 
>> It would also be great if you could run the optimizer for 9.7.1 before
>> you push a commit that contains changes of the P4 code as long as
>> we're stuck with that version (due to the APS BSP).  I understand that
>> you don't have your own build of 9.7.1 around but this could be done
>> easily in your workflow with the development shell from the SDE Nix
>> package. Right now I'm doing the optimization myself in retrospect but
>> then we will continue to have commits that fail until I push a fix for
>> broken profiles.
>>