Skip to content
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

[WFCORE-6679]: ManagementReadXmlTestCase inputs are too fragile. #5851

Merged
merged 3 commits into from
Mar 1, 2024

Conversation

ehsavoie
Copy link
Contributor

  • Generating the servers configuration through scripts to make them less fragile.

Jira: https://issues.redhat.com/browse/WFCORE-6679

@github-actions github-actions bot added the deps-ok Dependencies have been checked, and there are no significant changes label Jan 29, 2024
@yersan
Copy link
Collaborator

yersan commented Feb 8, 2024

Hi @ehsavoie , sadly this got a conflict because domain/ManagementReadXmlTestCase.java was moved to domain/suites/ManagementReadXmlTestCase.java :(, could you rebase it?

@ehsavoie
Copy link
Contributor Author

ehsavoie commented Feb 8, 2024

@yersan done

@wildfly-ci

This comment was marked as off-topic.

Copy link
Collaborator

@yersan yersan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added some comments, but in any case, it seems current failures are relevant to this PR

@@ -0,0 +1,71 @@
<?xml version="1.0" encoding="UTF-8"?>
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this could be removed and used as a base for the domain-configs/domain-standard.xml which is indeed the base configuration used to start the domain for DomainTestSupport

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't understand

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This test is about checking the runtime configuration of a managed server thus this base XML file is here to help produce the expected runtime configuration of those managed servers.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ehsavoie Sorry for the delay providing feedback about this. My comment here does not make sense, as you stated before, although this is a domain mode test, we are interested in getting the managed server configuration and I pointed you out to our domain standard config

@wildfly-ci

This comment was marked as outdated.

@wildfly-ci

This comment was marked as outdated.

@yersan
Copy link
Collaborator

yersan commented Feb 27, 2024

@ehsavoie ManagementReadXmlTestCase has failed repeatedly in Windows, could you take a look?

 * Generating the servers configuration through scripts to make them
   less fragile.

Jira: https://issues.redhat.com/browse/WFCORE-6679

Signed-off-by: Emmanuel Hugonnet <[email protected]>
@wildfly-ci
Copy link

Core -> Full Integration Build 13526 outcome was UNKNOWN using a merge of 2f5d7e9
Summary: Canceled (Error while applying patch; cannot find commit 292ad53 in the https://github.com/wildfly/wildfly-core.git repository, possible reason: refs/pull/5851/merge branch was updated and the commit selected for the ... Build time: 00:00:31

@wildfly-ci

This comment was marked as outdated.

@wildfly-ci

This comment was marked as outdated.

@yersan yersan added the ready-for-merge This PR is ready to be merged and fulfills all requirements label Mar 1, 2024
@yersan yersan merged commit 4c8a222 into wildfly:main Mar 1, 2024
12 checks passed
@yersan
Copy link
Collaborator

yersan commented Mar 1, 2024

Thanks @ehsavoie

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
deps-ok Dependencies have been checked, and there are no significant changes ready-for-merge This PR is ready to be merged and fulfills all requirements
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants