-
Notifications
You must be signed in to change notification settings - Fork 434
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
Random Process 'command '/usr/lib/jvm/java-17-openjdk-amd64/bin/java'' finished with non-zero exit value 1 #1908
Comments
@shanman190 🙏 anything comes to your mind about this? |
It's caused by some contact content.. bisecting now |
I think it's caused by using |
|
It seems its not only that, adding more contracts with various contents causes this failure |
Can you please create a reproducer for this? Go to start.spring.io and generate a new project and create a project that causes this issue? |
That will be rather difficult given the size of my project |
I have nailed down the other cause of failures, it was a typo in the contract. In this case the problems is
I think the plugin should do a better job at reporting the internal error. |
Just adding a contract like this causes the error to appear:
|
So this is likely an error with the generator code itself which is being run in the background with the |
How can I add the debug flag when running this from gradle plugin? |
This turns on Gradle debug logging which will include the stdout logs from |
I think the failure is
So kind of working as expected, but showing the user just |
@shanman190 anything else we can do here to provide that output in a visible place to the user? |
@marcingrzejszczak, one thing that I've been considering here is to capture the stdout and stderr streams separately. Then when the process exits in error and we would go to throw the Gradle exception, we could probably send the stderr stream to the Gradle logger so that users can see it. The only possible hold up to this would be needing to ensure that the logging in place uses the correct streams based upon the logging level used. |
Sounds good to me! We could for starters ensure that we're logging exceptions correctly. I don't think at this point other information is that important, WDYT? |
That sounds good to me and about what I had in mind also. |
@shanman190 can you file a PR against 3.1.x branch? I will merge things forward (if I encounter any issues I'll ping you back) |
Describe the bug
Suddenly gradle stopped building because of an error when generating contract tests.
I'm using version 3.0.5
The text was updated successfully, but these errors were encountered: