the irritation i was expressing was because previous time we asked peopel not to recheck with out a reason was not implemented as asking people to trying and see if they can fix the underlying problem.
repeating * STOP DOING BLIND RECHECKS aka. 'recheck' https://docs.openstack.org/project-team-guide/testing.html#how-to-handle-tes...
in the gate status section of our meeting every week and not actually trying to understand the reasons people were giving for a recheck was unhelpful and franckly quite annoying.
That document has lots of good examples and suggestions for exactly what we’re trying to do: get people to examine the failures. The most common thing I hear when I confront people about why they’re rechecking is that they “don’t know how to debug this stuff”. So I think pointing them at a document that gives them pointers and places to start is pretty good.
but when i saw in our team meeting this week it very triggering as we prviously had agreed to stop doing that as a team
* please avoid bare rechecks (bauzas, 16:12:14) * ACTION: bauzas to tell about the bare rechecks every week in our meeting (bauzas, 16:15:26)
ill chat to bauzas about how we can phase this reminder to make it cleare the focus is not about stoping blind recheck its about understanding why a recheck was required and fixing that issue and providing a reasons is the minimal first step in that process.
It’s unfortunate that you’re triggered by a reminder, but it’s also like the least impactful thing in the meeting. It gets said, and then immediately we move on to the next thing. Could you maybe just read it with the new lens of understanding where it's coming from from now on? —-Dan