From 84a96ceb421aae8644d04ef559819e6f4cd8041d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Petr=20=C5=A0pl=C3=ADchal?= <psplicha@redhat.com>
Date: Tue, 8 Oct 2024 15:11:56 +0200
Subject: [PATCH] Remove `skip` from the `ResultInterpret` enumeration

As discussed today, the `skip` value was never documented in the
test `result` key specification and was added by an accident.

There seems to be a use case to support skipping selected tests
but that functionality is substantially different from the result
interpretation configured by the `result` key which happens only
after test execution is completed so most probably a new test key
should be introduced for it.
---
 tmt/result.py           | 1 -
 tmt/schemas/common.yaml | 1 -
 2 files changed, 2 deletions(-)

diff --git a/tmt/result.py b/tmt/result.py
index 546346afa6..bfc803fe47 100644
--- a/tmt/result.py
+++ b/tmt/result.py
@@ -47,7 +47,6 @@ class ResultInterpret(enum.Enum):
     INFO = 'info'
     WARN = 'warn'
     ERROR = 'error'
-    SKIP = 'skip'
 
     # Special interpret values
     RESPECT = 'respect'
diff --git a/tmt/schemas/common.yaml b/tmt/schemas/common.yaml
index 220a5d1282..0a160b4867 100644
--- a/tmt/schemas/common.yaml
+++ b/tmt/schemas/common.yaml
@@ -478,7 +478,6 @@ definitions:
       - warn
       - error
       - fail
-      - skip
       - custom
       - restraint