Skip to content

Conversation

skocjan
Copy link

@skocjan skocjan commented Sep 16, 2025

If TEST_ASSERT_*_MESSAGE() is used and fails, next message is printed on the same line without EOL. This change should improve the readability of output.

If TEST_ASSERT_*_MESSAGE() is used and fails, next message is printed on the same line
without EOL. This change should improve the readability of output.
@mvandervoord
Copy link
Member

Hi @skocjan -- what is the situation you're running into where this line ending was necessary? Normally, a line ending is automatically added in UnityConcludeTest after each test, so that the individual functions and macros don't have to add it themselves. This will be true no matter if a custom message has been added or not. I'm assuming, though, since you've attempted to fix something, that you've seen a problem in some configuration. Can you tell me more about what you're seeing and what your configuration is?

@skocjan
Copy link
Author

skocjan commented Sep 30, 2025

Hi @mvandervoord , thanks for explaination. My configuration is a cross compilation to TI ARM platform and to be honest, it must've been some misinterpretation from my side, because now, when I have it properly integrated, I cannot see the issue anymore. Sorry for the noise and PR can be closed

@skocjan skocjan closed this Sep 30, 2025
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.

2 participants