Skip to content

Conversation

@dreiss
Copy link

@dreiss dreiss commented Jan 23, 2023

No description provided.

@dreiss
Copy link
Author

dreiss commented Jan 23, 2023

This is meant to be rebased and merged as two separate commits. Please let me know if I didn't format the PR properly for that.

Copy link
Member

Choose a reason for hiding this comment

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

I'm not a particular owner of this file, but I'd be hesitant to add a class here for a single example that only shows string formatting.

Copy link
Contributor

Choose a reason for hiding this comment

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

I'm not seeing the benefit of making a class from this, can be done inline on line 218

Copy link
Contributor

Choose a reason for hiding this comment

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

I'm not seeing the benefit of making a class from this, can be done inline on line 218

@dreiss
Copy link
Author

dreiss commented Jan 24, 2023

Doing it inline forces all of the string formatting to be done even if debug logs are turned off. Putting it in an object delays the formatting and skips it all together if the log is not rendered. In general, I prefer not to do expensive operations in debug logs for performance reasons, but this is not a performance-critical codepath, so maybe it would be okay. Please let me know your preference.

@aaronemassey
Copy link
Member

Doing it inline forces all of the string formatting to be done even if debug logs are turned off

That's a good point! Since we're not just using the string formatting provided by the logger we don't get the benefit of lazy formatting from the logger.

However:

but this is not a performance-critical codepath

I'd rather have a nominal increase in compute cost, especially if not performance-critical, instead of adding an additional type.

If this changes we can always add the class or use lazy-string but I don't foresee this to happen.

@dreiss
Copy link
Author

dreiss commented Jan 26, 2023

Updated. Is this ready to rebase+merge?

@aaronemassey
Copy link
Member

Updated. Is this ready to rebase+merge?

Fine with me, but you should get a review from a proper maintainer of twister. I'd recommend the pr help channel in the discord.

aaronemassey
aaronemassey previously approved these changes Jan 27, 2023
@dreiss
Copy link
Author

dreiss commented Jan 27, 2023

@nashif is listed as the Twister maintainer.

@aaronemassey aaronemassey requested a review from yperess January 27, 2023 21:54
@dreiss
Copy link
Author

dreiss commented Jan 31, 2023

@nashif or @yperess , is this ready to be merged?

yperess
yperess previously approved these changes Jan 31, 2023
@dreiss dreiss dismissed stale reviews from yperess and aaronemassey via eaaf898 February 3, 2023 22:46
@dreiss dreiss force-pushed the pytest-1 branch 2 times, most recently from eaaf898 to f78e460 Compare February 6, 2023 17:20
@dreiss
Copy link
Author

dreiss commented Feb 6, 2023

Any ideas about this failure? I locally ran west twister -p qemu_x86_64 -s tests/lib/mpsc_pbuf/libraries.mpsc_pbuf_concurrent, and it passes.

David Reiss added 2 commits February 7, 2023 09:07
The option is "cmdopt"

Signed-off-by: David Reiss <[email protected]>
This makes it easy to run the command manually, possibly with edits to
change the test behavior.

Signed-off-by: David Reiss <[email protected]>
@dreiss
Copy link
Author

dreiss commented Feb 8, 2023

Looks like it was fixed by rebasing. Can this be merged?

@stephanosio stephanosio added this to the v3.4.0 milestone Feb 14, 2023
@stephanosio
Copy link
Member

Looks like it was fixed by rebasing. Can this be merged?

We are currently in hard freeze for 3.3 and only blocker bug fixes and documentation changes can be merged now. The merge window will open next week.

@nashif nashif merged commit 2d8271d into zephyrproject-rtos:main Feb 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants