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

Cleanup Core Profle TCK runner #58

Merged
merged 3 commits into from
Oct 27, 2022

Conversation

scottmarlow
Copy link
Contributor

#57

wf-core-tck-runner/pom.xml Outdated Show resolved Hide resolved
wf-core-tck-runner/rest-tck/pom.xml Outdated Show resolved Hide resolved
# locate SPEC API jars if not already specified
if [[ -z "${ANNOTATION_API}" ]]; then
pushd ${JBOSS_HOME}
export ANNOTATION_API=`find * -name jakarta*annotation*api*.jar`
Copy link
Member

Choose a reason for hiding this comment

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

Does this work with the embedded \n new lines?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

which \n new lines do you mean?

Copy link
Member

Choose a reason for hiding this comment

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

When you do a find it will print each found file on a new line. You'd end up with the environment variable looking something like:

ANNOTATION_API=some/path/cool.jar
some/path/other.jar
some/path/another.jar

I would think only the first one, cool.jar in the example, would be seen.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

If multiple jars match the pattern than we need to update the find expression. That sounds like a condition we should check for

Copy link
Member

Choose a reason for hiding this comment

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

Ah, I guess all these do just return a single JAR. Maybe something we more need to keep an eye on then.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Agreed and the run will fail with an error if we introduce additional jars that have similar names such that more than one line is in the result.

@scottmarlow
Copy link
Contributor Author

Are we ready to merge this PR or do we need more changes?

@scottmarlow
Copy link
Contributor Author

scottmarlow commented Oct 27, 2022

@jamezp @bstansberry

Could we merge this change as It seems like this change helps avoid some Core Profile 10 failures.

Testing without this pr:

failures=[ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.416 s <<< FAILURE! - in ee.jakarta.tck.ws.rs.jaxrs21.ee.sse.ssebroadcaster.JAXRSClientIT [ERROR] Tests run: 2654, Failures: 1, Errors: 0, Skipped: 59 [ERROR] Tests run: 4, Failures: 2, Errors: 1, Skipped: 0, Time elapsed: 9.286 s <<< FAILURE! - in ee.jakarta.tck.core.rest.jsonb.cdi.CustomJsonbSerializationIT [ERROR] Tests run: 13, Failures: 2, Errors: 1, Skipped: 0
errors=[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3.133 s <<< FAILURE! - in ee.jakarta.tck.jsonp.signaturetest.jsonp.JSONPSigTest [ERROR] Tests run: 179, Failures: 0, Errors: 1, Skipped: 0 [ERROR] Tests run: 4, Failures: 2, Errors: 1, Skipped: 0, Time elapsed: 9.286 s <<< FAILURE! - in ee.jakarta.tck.core.rest.jsonb.cdi.CustomJsonbSerializationIT [ERROR] Tests run: 13, Failures: 2, Errors: 1, Skipped: 0

Testing with this pr:

At least one test failed!
failures=[ERROR] Tests run: 4, Failures: 2, Errors: 1, Skipped: 0, Time elapsed: 10.072 s <<< FAILURE! - in ee.jakarta.tck.core.rest.jsonb.cdi.CustomJsonbSerializationIT
[ERROR] Tests run: 13, Failures: 2, Errors: 1, Skipped: 0
errors=[ERROR] Tests run: 4, Failures: 2, Errors: 1, Skipped: 0, Time elapsed: 10.072 s <<< FAILURE! - in ee.jakarta.tck.core.rest.jsonb.cdi.CustomJsonbSerializationIT
[ERROR] Tests run: 13, Failures: 2, Errors: 1, Skipped: 0

@scottmarlow
Copy link
Contributor Author

We still need to understand why ee.jakarta.tck.core.rest.jsonb.cdi.CustomJsonbSerializationIT is failing but it is good to see the ee.jakarta.tck.jsonp.signaturetest.jsonp.JSONPSigTest passing with this pr.

@bstansberry bstansberry merged commit 115cec9 into wildfly:main Oct 27, 2022
@bstansberry
Copy link
Contributor

Thanks @scottmarlow

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants