You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nuttx.apache.org by "btashton (via GitHub)" <gi...@apache.org> on 2023/02/07 16:19:13 UTC

[GitHub] [nuttx] btashton commented on pull request #8452: sched_note: add SCHED_NOTE_CUSTOM_BEGIN/END interface

btashton commented on PR #8452:
URL: https://github.com/apache/nuttx/pull/8452#issuecomment-1421045563

   > @xiaoxiang781216 after reviewing PR #8454 I started thinking about this idea: include an automatic "Before and After binary size increment" on our CI. This way we don't need to ask people to verify how much that patch increased NuttX size. What do you think? Any idea how to do that? Maybe @btashton has some suggest he knows a lot about this CI logic.
   
   I did start building something like this a while back, but was only going to do it on master where getting the baseline is much easier. I already set CI up to generate an artifact with the build outputs from all the builds with the intention of being able to compare this data. 
   
   I started building something here 
   https://github.com/btashton/nuttx-testnom


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@nuttx.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org