On 05.05.2017 18:56, Adam Williamson wrote:
> On Wed, 2017-05-03 at 14:51 +0200, Stef Walter wrote:
>> On 02.05.2017 17:47, Adam Williamson wrote:
>>> On Tue, 2017-05-02 at 11:57 +0300, Marius Vollmer wrote:
>>>> Adam Williamson <[email protected]> writes:
>>>>
>>>>> Until recently we ran these tests only on Fedora's nightly development
>>>>> release distribution composes. Recently, though, we deployed some
>>>>> enhancements to our openQA setup that let us run tests on Fedora
>>>>> distribution updates as well, and have the results made visible
>>>>> through the Fedora update system (Bodhi). I have just made it so that,
>>>>> from now on, these tests will run on any update that contains the
>>>>> 'cockpit' package. They also run on any critical path update.
>>>>
>>>> Nice!
>>>>
>>>> What happens when a test fails?  Do we get a notification somehow?
>>>
>>> For now no, you have to keep an eye on the 'Automated Tests' tab in
>>> Bodhi; I'd recommend taking a look at that for every update anyway,
>>> it's good to know the Taskotron results also.
>>>
>>> I'm planning to look at whether we can hook up some FMN options for
>>> test results, but I haven't had time to start on that yet.
>>
>> How can I affect the results I see? I see dist.rpmgrill and
>> dist.rpmgrill.desktop-lint failures. Those failures are false-positives.
>> Is there a rpmgrill configuration file I can place in our dist-git
>> directory that will affect those results and remove the false positives?
> 
> Kamil sends along a couple of notes:
> 
> 1. You can set up notifications in FMN for each taskotron result on your
> package which is FAILED/NEEDS_INSPECTION (for example, or just for results
> for tasks starting with "dist.rpmgrill", etc). See some more in
> https://mkrizek.wordpress.com/2016/02/24/taskotron-results-notifications/
> 
> 2. We don't support config files for rpmlint, rpmgrill and other generic
> tasks at the moment, unfortunately. But we know it needs to get done and is
> definitely in our plans.

Cool. Looking forward to that. We'll start to pay attention to those
tests once we as developers/packagers have a chance of making them green.

Cheers,

Stef


Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
cockpit-devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to