ChanServ changed the topic of #etnaviv to: #etnaviv - the home of the reverse-engineered Vivante GPU driver - Logs https://oftc.irclog.whitequark.org/etnaviv
pcercuei has quit [Quit: dodo]
Surkow|laptop has quit [Ping timeout: 480 seconds]
mvlad has joined #etnaviv
frieder has joined #etnaviv
lynxeye has joined #etnaviv
<lynxeye> austriancoder: What's the process to shrink the CI flakes file? I suspect that some of the tests marked as flakes are fixed in the meantime, but once they are in the flakes file they are just accepted with any result. Is there any way to see if tests from the flakes list consistently passed for the last N number of runs and could potentially be removed from flakes?
chewitt has joined #etnaviv
pcercuei has joined #etnaviv
<austriancoder> lynxeye: there is no automatic way - re-run full suite few times and regenerate flakes time to time
f_ has joined #etnaviv
f_ has quit [Remote host closed the connection]
f_ has joined #etnaviv
<austriancoder> I might have time next week do work on this task
<lynxeye> austriancoder: Okay, I might also look at this from time to time. It's just a trend I noticed that the flakes get added from the nightly runs and then just stay there if one doesn't actively look for things that might have been fixed by a specific commit. Which in turn means that we might overlook actual regressions as things are still flagged as flaky.
f_ has quit [Ping timeout: 480 seconds]
* lynxeye hates TS for all the additional state it needs, but still loves it for the sake of performance
* austriancoder too.. have a nice blt patch series but need to debug a TS issue
f_ has joined #etnaviv
lynxeye has quit [Quit: Leaving.]
mvlad has quit [Remote host closed the connection]
frieder has quit [Remote host closed the connection]
chewitt has quit [Quit: Zzz..]
Surkow|laptop has joined #etnaviv
f_ has quit [Remote host closed the connection]
f_ has joined #etnaviv
f_ has quit [Ping timeout: 480 seconds]
pcercuei has quit [Quit: dodo]