kicad-developers team mailing list archive

[Wayne Stambaugh <stambaughw@xxxxxxxxx>]

Adam,

I know you are busy so I wont ask for a CI job that just builds the
KiCad executables even though that would be my preference.  I suppose we
could try the special word idea and see how it pans out.  If it becomes
too noisy, we could always disable it.

Wayne

On 4/24/19 2:02 PM, Adam Wolf wrote:
> I do not have a job like that for macOS at this point, so things like
> "brew broke an upstream thing" would also show up.
> 
> These are not super common, but I could also put a special word in all
> of the build emails so people can easily filter them out.
> 
> Or, I can wait on doing anything and create a job that just builds.
> 
> Adam
> 
> On Wed, Apr 24, 2019 at 12:48 PM Wayne Stambaugh <stambaughw@xxxxxxxxx> wrote:
>>
>> I wouldn't have an issue with forwarding build errors to the dev mailing
>> list as long as the build failure messages were limited to compile/link
>> errors due to broken source repo commits.  I don't think it's necessary
>> for devs to see all of the other unrelated build issues.  I don't know
>> if it would be possible to segregate out the compile/link errors.  I
>> don't know that a separate mailing list is warranted.  I'm already on
>> too many mailing lists ;)
>>
>> Wayne
>>
>> On 4/24/2019 1:07 PM, Adam Wolf wrote:
>>> I will set up a new view for the macbuilder that should be all green,
>>> and I can also set it up to push build failures to a list.
>>>
>>> Does it make sense to have all the builders email a new list that
>>> committers and packages can watch?
>>>
>>> Adam
>>>
>>> On Wed, Apr 24, 2019, 11:38 AM John Beard <john.j.beard@xxxxxxxxx
>>> <mailto:john.j.beard@xxxxxxxxx>> wrote:
>>>
>>>     On Wed, Apr 24, 2019 at 4:51 PM Steven A. Falco
>>>     <stevenfalco@xxxxxxxxx <mailto:stevenfalco@xxxxxxxxx>> wrote:
>>>      >
>>>      > It is not quite a CI builder, but there is also the Fedora
>>>     nightly that happens on Copr:
>>>      > https://copr.fedorainfracloud.org/coprs/g/kicad/kicad/
>>>
>>>     That's useful to know, thanks
>>>
>>>      > I see some failures there on kicad2step.  Here is a
>>>     representative sample from the Rawhide build:
>>>
>>>     Should be fixed now (static vs shared libs). Issue only exists on
>>>     master.
>>>
>>>     Cheers,
>>>
>>>     John
>>>
>>>     _______________________________________________
>>>     Mailing list: https://launchpad.net/~kicad-developers
>>>     Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
>>>     <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
>>>     Unsubscribe : https://launchpad.net/~kicad-developers
>>>     More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>>> _______________________________________________
>>> Mailing list: https://launchpad.net/~kicad-developers
>>> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
>>> Unsubscribe : https://launchpad.net/~kicad-developers
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp