On Wed, May 11, 2022 at 03:06:47PM +1000, Dave Airlie wrote: > > And use it to store expectations about what the drm/msm driver is > > supposed to pass in the IGT test suite. > > I wanted to loop in Linus/Greg to see if there are any issues raised > by adding CI results file to the tree in their minds, or if any other > subsystem has done this already, and it's all fine. Why does the results need to be added to the tree? Shouldn't they be either "all is good" or "constantly changing and a constant churn"? > I think this is a good thing after our Mesa experience, but Mesa has a > lot tighter integration here, so I want to get some more opinions > outside the group. For systems that have "tight integration" this might make sense as proof that all is working for a specific commit, but I can't see how this will help the kernel out much. What are you going to do with these results being checked in all the time? thanks, greg k-h
