On Wed, Oct 02, 2024 at 03:10:14PM GMT, Jani Nikula wrote:
> On Wed, 25 Sep 2024, Maxime Ripard wrote:
> > On Wed, Sep 25, 2024 at 01:52:02PM GMT, Simona Vetter wrote:
> >> I think for at least drm the consensus is clear, we won't have kunit tests
> >> that splat.
> >
> > Where was that ever discu
On Wed, 25 Sep 2024, Maxime Ripard wrote:
> On Wed, Sep 25, 2024 at 01:52:02PM GMT, Simona Vetter wrote:
>> I think for at least drm the consensus is clear, we won't have kunit tests
>> that splat.
>
> Where was that ever discussed?
Well, where was it ever agreed that it's okay for drm kunit test
On Wed, Sep 25, 2024 at 09:04:39AM GMT, Guenter Roeck wrote:
> On 9/25/24 06:05, Maxime Ripard wrote:
> [ ... ]
>
> > > We've had similar discussions in the past around unit tests that wasted
> > > too much cpu time with randomized combinatorial testing, and we've thrown
> > > those out too from d
On 9/25/24 06:05, Maxime Ripard wrote:
[ ... ]
We've had similar discussions in the past around unit tests that wasted
too much cpu time with randomized combinatorial testing, and we've thrown
those out too from drm. Test hygiene matters.
We had that discussion because those tests could run fo
On 9/25/24 05:59, Maxime Ripard wrote:
...
All I'm saying it generates an extra burden for current real world CI
systems that run tests on a massive scale and even have paid
maintainers. It's not trivial to sort out expected and unexpected
warnings, and keep the filters updated every time the wa
On Wed, Sep 25, 2024 at 01:52:02PM GMT, Simona Vetter wrote:
> On Tue, Sep 24, 2024 at 08:09:38AM -0700, Guenter Roeck wrote:
> > On 9/24/24 06:56, Maxime Ripard wrote:
> > > On Tue, Sep 24, 2024 at 06:37:59AM GMT, Guenter Roeck wrote:
> > > > On 9/24/24 04:54, Maxime Ripard wrote:
> > > > > +Guent
On Wed, Sep 25, 2024 at 12:41:40PM GMT, Jani Nikula wrote:
> On Tue, 24 Sep 2024, Maxime Ripard wrote:
> > On Tue, Sep 24, 2024 at 06:56:26PM GMT, Jani Nikula wrote:
> >> On Tue, 24 Sep 2024, Guenter Roeck wrote:
> >> On Tue, Sep 24, 2024 at 12:06:28PM GMT, Simona Vetter wrote:
> >> > Ye
On Tue, Sep 24, 2024 at 08:09:38AM -0700, Guenter Roeck wrote:
> On 9/24/24 06:56, Maxime Ripard wrote:
> > On Tue, Sep 24, 2024 at 06:37:59AM GMT, Guenter Roeck wrote:
> > > On 9/24/24 04:54, Maxime Ripard wrote:
> > > > +Guenter
> > > >
> > > > On Tue, Sep 24, 2024 at 12:06:28PM GMT, Simona Vett
On Tue, 24 Sep 2024, Maxime Ripard wrote:
> On Tue, Sep 24, 2024 at 06:56:26PM GMT, Jani Nikula wrote:
>> On Tue, 24 Sep 2024, Guenter Roeck wrote:
>> On Tue, Sep 24, 2024 at 12:06:28PM GMT, Simona Vetter wrote:
>> > Yeah I think long-term we might want a kunit framework so that we can
>
On 9/24/24 09:57, Maxime Ripard wrote:
On Tue, Sep 24, 2024 at 06:56:26PM GMT, Jani Nikula wrote:
On Tue, 24 Sep 2024, Guenter Roeck wrote:
On Tue, Sep 24, 2024 at 12:06:28PM GMT, Simona Vetter wrote:
Yeah I think long-term we might want a kunit framework so that we can
catch dmesg warnings w
On Tue, Sep 24, 2024 at 06:56:26PM GMT, Jani Nikula wrote:
> On Tue, 24 Sep 2024, Guenter Roeck wrote:
> On Tue, Sep 24, 2024 at 12:06:28PM GMT, Simona Vetter wrote:
> > Yeah I think long-term we might want a kunit framework so that we can
> > catch dmesg warnings we expect and test f
On 9/24/24 08:56, Jani Nikula wrote:
On Tue, 24 Sep 2024, Guenter Roeck wrote:
On Tue, Sep 24, 2024 at 12:06:28PM GMT, Simona Vetter wrote:
Yeah I think long-term we might want a kunit framework so that we can
catch dmesg warnings we expect and test for those, without those warnings
actually g
On Tue, 24 Sep 2024, Guenter Roeck wrote:
On Tue, Sep 24, 2024 at 12:06:28PM GMT, Simona Vetter wrote:
> Yeah I think long-term we might want a kunit framework so that we can
> catch dmesg warnings we expect and test for those, without those warnings
> actually going to dmesg. Sim
On 9/24/24 06:56, Maxime Ripard wrote:
On Tue, Sep 24, 2024 at 06:37:59AM GMT, Guenter Roeck wrote:
On 9/24/24 04:54, Maxime Ripard wrote:
+Guenter
On Tue, Sep 24, 2024 at 12:06:28PM GMT, Simona Vetter wrote:
On Tue, Sep 17, 2024 at 08:43:50PM +0300, Jani Nikula wrote:
The tests consistently
On Tue, Sep 24, 2024 at 06:37:59AM GMT, Guenter Roeck wrote:
> On 9/24/24 04:54, Maxime Ripard wrote:
> > +Guenter
> >
> > On Tue, Sep 24, 2024 at 12:06:28PM GMT, Simona Vetter wrote:
> > > On Tue, Sep 17, 2024 at 08:43:50PM +0300, Jani Nikula wrote:
> > > > The tests consistently trigger WARNs in
On 9/24/24 04:54, Maxime Ripard wrote:
+Guenter
On Tue, Sep 24, 2024 at 12:06:28PM GMT, Simona Vetter wrote:
On Tue, Sep 17, 2024 at 08:43:50PM +0300, Jani Nikula wrote:
The tests consistently trigger WARNs in drm_framebuffer code. I'm not
sure what the point is with type of belts and suspende
+Guenter
On Tue, Sep 24, 2024 at 12:06:28PM GMT, Simona Vetter wrote:
> On Tue, Sep 17, 2024 at 08:43:50PM +0300, Jani Nikula wrote:
> > The tests consistently trigger WARNs in drm_framebuffer code. I'm not
> > sure what the point is with type of belts and suspenders tests. The
> > warnings *are*
On Tue, Sep 17, 2024 at 08:43:50PM +0300, Jani Nikula wrote:
> The tests consistently trigger WARNs in drm_framebuffer code. I'm not
> sure what the point is with type of belts and suspenders tests. The
> warnings *are* the way to flag erroneous API usage.
>
> Warnings in turn trigger failures in
The tests consistently trigger WARNs in drm_framebuffer code. I'm not
sure what the point is with type of belts and suspenders tests. The
warnings *are* the way to flag erroneous API usage.
Warnings in turn trigger failures in CI. Filtering the warnings are
error prone, and, crucially, would also
19 matches
Mail list logo
