openstack
/
project-team-guide
Code Issues Proposed changes

Add info about recheck comments with "unrelated failure" info 

We have seen such comments a lot recently, since we started to monitor
"bare rechecks" more and comments with just info about unrelated failure
is really as meaningless as simple 'bare recheck'.

This patch adds info about such 'almost' bare rechecks and that those
should be also avoided.

Change-Id: I89b4ba132f7b304b71ae101ebce2695c55039a13
This commit is contained in:
Slawek Kaplonski 2024-03-25 09:18:57 +01:00
parent 8f25583cab
commit 46230c7162
1 changed files with 7 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
doc/source/testing.rst
View File

@ -110,9 +110,13 @@ time), so please be extremely sparing when asking the system to re-run
tests.
.. note:: Please do not **EVER** simply ``recheck`` without a
reason. Even if that reason is "I don't know", please
indicate that you at least *attempted* to determine the
reason for the failure.
reason. Please always *attempt* to determine the reason for the
failure and give some meaningful reason of why recheck needs to
be done. It can be something like name of the test(s) which have
failed or some other info about what and in which job/test case
went wrong.
Please try to avoid comments like ``recheck - unrelated failure`` as
such comments are almost the same as simply ``recheck`` without any
It is important that before you request a recheck, you adhere to the
following guidelines: