Fix Polarion test case ID matching in modifyE2ETags.py#27
Open
tusharjadhav3302 wants to merge 1 commit into
Open
Fix Polarion test case ID matching in modifyE2ETags.py#27tusharjadhav3302 wants to merge 1 commit into
tusharjadhav3302 wants to merge 1 commit into
Conversation
tusharjadhav3302
requested review from
chenwng,
dlaw4608,
ekuris-redhat,
eshulman2,
gryf,
imatza-rh,
mandre,
stephenfin and
winiciusallan
as code owners
July 24, 2026 09:42
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
jump.py builds the Polarion match key as "classname.name" and
queries Polarion for entries matching those IDs. The XML produced
by modifyE2ETags.py had classname="no-testclass" (Ginkgo's
default, never overwritten) and an "OTP." prefix in the name
(from the [OTP] tag). This produced IDs like
"no-testclass.OTP.sig-installer.Suite_openshift_openstack..."
which matched nothing in Polarion. The empty query result caused
process_xml() to raise JumpException("Cannot proceed without xml
with tempest results").
Strip the "OTP." prefix and split the formatted name at the first
dot — first segment becomes classname, rest becomes name. This
produces classname="sig-installer" and name="Suite_openshift_
openstack.<category>.<description>", matching the 21 registered
automation-test-ids (RHOSO-11212 through RHOSO-11266).
Validated on serval70 with jump.py --dry_run=True (no
--no-mapping). Tests matched correctly against Polarion entries.
Related-Issue: OSPRH-32990
Co-authored-by: Cursor <cursoragent@cursor.com>
tusharjadhav3302
force-pushed
the
fix-polarion-classname-and-otp-prefix
branch
from
July 24, 2026 12:04
c545659 to
ba0f39d
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fix Polarion test case ID matching in modifyE2ETags.py to resolve the
"Cannot proceed without xml with tempest results" crash in jump.py.
Problem
jump.py builds the Polarion match key as
classname.name. The XML producedby modifyE2ETags.py had:
This produced IDs like
no-testclass.OTP.sig-installer.Suite_openshift_openstack...which don't match any registered Polarion entries. The Polarion query returned
an empty dict, causing the JumpException crash.
Fix
OTP.prefix (comes from the[OTP]tag in openshift-tests output)classname,rest becomes
nameBefore/After
Before: classname="no-testclass" name="OTP.sig-installer.Suite_openshift_openstack.lb..." → match key: no-testclass.OTP.sig-installer.Suite_openshift_openstack... (no Polarion match → crash)
After: classname="sig-installer" name="Suite_openshift_openstack.lb..." → match key: sig-installer.Suite_openshift_openstack... (matches RHOSO-11212 to RHOSO-11266)
Validation
Manually tested on serval70 with
jump.py --dry_run=True(no --no-mapping).Tests matched correctly against Polarion entries. Only legitimately skipped
tests (IPv6, Kuryr, Amphora) show warnings — expected behavior.
Related-Issue: OSPRH-32990