-
-
Notifications
You must be signed in to change notification settings - Fork 98
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support multiple required in features tag #614
Conversation
if (!isFeatureInTestFlags(testFlags, entry.getKey())) { | ||
return null; | ||
if (isFeatureInTestFlags(testFlags, entry.getKey())) { | ||
break; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With this change, if there is no test flag and feature match, the test will run. This is not expected behavior.
Grinder - test run with TEST_FLAG=empty.
Grinder: |
feature For example: https://hyc-runtimes-jenkins.swg-devops.com/job/Grinder/43462/ |
This existing logic in TKG is not straightforward. To make this simple, I think we should make assumption that we cannot use feature With this assumption, the logic can be updated to
@LongyuZhang what do you think? |
As I understand ,I think the the issue is when we are having 2 |
Grinder links : TEST_FLAG: EMPTY FIPS140_3_OpenJCEPlusFIPS.FIPS140-3 https://hyc-runtimes-jenkins.swg-devops.com/job/Grinder/43488/ FIPS140_3_OpenJCEPlusFIPS |
I assume that we cannot use feature required with other featureOpts. This is true with your current version. If required flag is matched, ignore other featureOpts. |
Discussed with @LongyuZhang , before this change, we need to update the existing playlist.xml. Otherwise, it will break existing testing.
Also, we should update the doc to clearly state the assumption:
|
@llxia Please find the draft PR: eclipse-openj9/openj9#20215 to remove CRIU featureOption. |
Please run TKG PR test. |
Grinder links: TARGET:jdk_other TEST_FLAG:FIPS140_3_OpenJCEPlusFIPS.FIPS140-3 TEST_FLAG:FIPS140_3_OpenJCEPlusFIPS TEST_FLAG:FIPS140_2 |
Can we update the title to reflect the change? Update feature flag handling for required features -> Support multiple required in features tag |
run tkg-test |
@annaibm TKG test build started, workflow Run ID: 11019710616 |
@annaibm Build(s) failed, workflow Run ID: 11019710616 |
278b548
to
bae4614
Compare
run tkg-test |
@annaibm TKG test build started, workflow Run ID: 11034601010 |
@annaibm Build(s) successful, workflow Run ID: 11034601010 |
|
||
if 'test_arch_390_z15_0' not in passed: | ||
skipped.add('test_arch_390_z15_0') | ||
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please remove extra space
- Removed `null` statement from `required` feature check to ensure all required features are processed. - Allows the code to continue checking all feature flags, even after finding a required flag in `testFlags`. - Added test_not_arch_390_z15plus_0 into passed list for running TKG test PR in github actions as no microarch version is detected. related:https://github.ibm.com/runtimes/backlog/issues/1525 Signed-off-by: Anna Babu Palathingal <[email protected]>
Thanks @annaibm. Since TKG serves as the core framework layer, it could significantly impact testing behavior. For due diligence, could you please also run sanity.functional? Say, using JDK11 on xlinux. Compare with nightly runs and the TAP file info (TEST TARGETS RESULTS SUMMARY: TOTAL: xxx EXECUTED: xxx PASSED: xxx FAILED: xxx DISABLED: xxx SKIPPED: xxx) should be the same. |
Grinder link:
Comparison with nightly -> https://hyc-runtimes-jenkins.swg-devops.com/job/Test_openjdk11_j9_sanity.functional_x86-64_linux/931/tapTestReport/
TEST TARGETS SUMMARY:
TEST TARGETS SUMMARY:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @annaibm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
null
statement fromrequired
feature check to ensure all required features are processed.testFlags
.related:https://github.ibm.com/runtimes/backlog/issues/1525