-
Notifications
You must be signed in to change notification settings - Fork 66
'GreetingServiceTest' from wildfly booster is failing in Che #2152
Comments
I found this issue running on |
I get a different error when running mvn clean install from the terminal or as a command. The default command is |
@eivantsov is that the whole log you are getting? That's a bit blurry to reason what is really going on. |
As you can see, maven is invoked in root dir rather than path to pom.xml is passed as an arg By the way, I have run
But ended well in the end. Same result when building locally in a Docker container. I suspect that the error has smth to do with permissions that an arbitrary user has in an OSO pod. |
Provided more details in #2262 to only realize that it's a duplicate of this issue, so pasting it here to avoid looping through tabs: Steps to reproduce
Prerequisites if starting from scratch:
(alternatively, clone this repository https://github.com/lordofthejars/swarmq where all the steps are already applied) Detailed stack tracesError while running Che (after clean build of the project)
Error while running from Maven (mvn test -Dtest=GreetingServiceTest)
|
@ibuziuk I have run tests on Docker and OpenShift, without Che at all. Tests fail with exact same error. Tests were held on a local Docker and Origin, as well as on OSO Pro. I can share OpenShift deployment yaml so that you can quickly test it locally as well. It is interesting that commands:
cause different behavior. The former just makes tests hang with a message:
We should probably get some input from arquillian team? Update. On ORO Pro, the process is killed even though I have enough RAM to run such a test. |
@eivantsov That makes sense with what I have observed. It doesn't look like OpenShift kills the process because it's using too much memory (there would be an evidence in the openshfit events). What we should look at are the |
We never really finished to tune |
@slemeur this is the last P0 that is not addressed from che side. Are we ok to add flag for skipping tests in wildfly commands as a temp workaround ? I'm afraid we will not be able to provide better fix before summit |
Fine for me as a temporary solution. |
I never worked for me in Docker. We should probably ask for help from WildFly or Arquillian devs |
@maxandersen do you happen to know who is the wildfly quickstart mainatainer ? |
hmmm.. adding
|
We figured out that even by skipping the test from the che command, we are not able to build the application. See: #3463 |
PR with updating wildfly recipe is send https://github.com/redhat-developer/che-dockerfiles/pull/35 let's see if it improve the situation |
Where is the PR ? |
https://github.com/redhat-developer/che-dockerfiles/pull/35? However, I don't see how it can help with oom when running maven build via exec... |
updated the comment |
Unfortumately, nothing changed after stack rebuilding :-( |
We would have a workaround provided in #3463 (comment) |
Workaround with disabling tests is already available on prod-preview - #3463 (comment) |
Adding |
Moved the issue to https://issues.jboss.org/browse/THORN-2049 as it's not to do with WildFly or Arquillian, it's to do with WildFly Swarm (now Thorntail) |
@ibuziuk I provided PR for the |
Is there any way to work around this and continue with the Getting Started? |
@bartoszmajsak sorry for the late response. Basically, |
A solved passing system property and force a layout System.setProperty("thorntail.filesystem.layout.class", "org.wildfly.swarm.internal.MavenFileSystemLayout"); A see the class FileSystemLayout.CUSTOM_LAYOUT_CLASS implementation. sorry my english |
Steps to reproduce:
The text was updated successfully, but these errors were encountered: