Skip to content

Conversation

@fl4via
Copy link

@fl4via fl4via commented Sep 19, 2021

@fl4via
Copy link
Author

fl4via commented Sep 19, 2021

I'm not sure if this fix is the best approach, and if there is need for a test, but this fix at least solved the problem in my reproducer, allowing me to see the stack trace of the fork error.

Comment on lines +656 to +661
else if ( forkClient.isErrorInFork() )
{
final StackTraceWriter stackTrace = forkClient.getErrorInFork();
booterForkException =
new SurefireBooterForkException( stackTrace.writeTraceToString() );
}
Copy link
Member

Choose a reason for hiding this comment

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

Please look line 711 - 733
StackTrace is printed if Maven command is started with -e option

Copy link
Contributor

Choose a reason for hiding this comment

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

@fl4via
Pls have a look at the comments and answers. How can we continue with this?

@jira-importer
Copy link

Resolve #2904

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.

4 participants