Skip to content

Conversation

@abutch3r
Copy link
Member

While the repeat logic caused the tests to run twice, due to the nature of how the configuration was managed, all that changed was EE11_FEATURES was added to the test and server names. the server configuration was left as is.

Use the RepeatTestFilter to determine if we are running the EE11 feature set and switch to the ee11 version of the configuration which includes the EE11 compatible feature set.

@abutch3r
Copy link
Member Author

abutch3r commented Nov 26, 2025

!build (view Open Liberty Personal Build - ❌ completed with errors/failures.)

Note: Target locations of links might be accessible only to IBM employees.

@abutch3r
Copy link
Member Author

abutch3r commented Nov 26, 2025

!build (view Open Liberty Personal Build - ❌ completed with errors/failures.)

Note: Target locations of links might be accessible only to IBM employees.

@LibbyBot
Copy link
Member

Code analysis and actions

DO NOT DELETE THIS COMMENT.
  • 50 FAT files were changed, added, or removed.

  • Check that the build did not break the affected FAT suite(s).

  • 3 test infrastructure code files were changed.

  • Test failures/errors in the build could be due to these changes.

  • Please describe in a separate comment how you tested your changes.

@LibbyBot
Copy link
Member

Code analysis and actions

DO NOT DELETE THIS COMMENT.
  • 50 FAT files were changed, added, or removed.

  • Check that the build did not break the affected FAT suite(s).

  • 3 test infrastructure code files were changed.

  • Test failures/errors in the build could be due to these changes.

  • Please describe in a separate comment how you tested your changes.

While the repeat logic caused the tests to run twice, due to the nature of how the configuration was managed, all that changed was EE11_FEATURES was added to the test and server names. the server configuration was left as is.

Use the RepeatTestFilter to determine if we are running the EE11 feature set and switch to the ee11 version of the configuration which includes the EE11 compatible feature set.
@abutch3r abutch3r force-pushed the jakartasec-ee-11-repeats-take-2 branch from 8802c95 to 73a69fd Compare November 27, 2025 10:10
@abutch3r
Copy link
Member Author

abutch3r commented Nov 27, 2025

!build
(view Open Liberty Personal Build - ❌ completed with errors/failures.)

Note: Target locations of links might be accessible only to IBM employees.

@LibbyBot
Copy link
Member

Code analysis and actions

DO NOT DELETE THIS COMMENT.
  • 50 FAT files were changed, added, or removed.

  • Check that the build did not break the affected FAT suite(s).

  • 3 test infrastructure code files were changed.

  • Test failures/errors in the build could be due to these changes.

  • Please describe in a separate comment how you tested your changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants