nuttxpr commented on PR #15997: URL: https://github.com/apache/nuttx/pull/15997#issuecomment-2727224462
[**\[Experimental Bot, please feedback here\]**](https://github.com/search?q=repo%3Aapache%2Fnuttx+13552&type=issues) This PR does NOT fully meet the NuttX requirements. Here's why: * **Summary is insufficient:** While it states *what* was changed, it doesn't explain *why* this change is necessary. What problem does the nesting of instrument loops cause? What are the symptoms? Why is this a bug that needs fixing? It also lacks a reference to a related NuttX issue. * **Impact is incomplete:** Simply stating "N/A" is not acceptable. While some sections *might* be N/A, the author needs to explicitly confirm that for each section. For example, the added compiler flag `-finstrument-functions` certainly has a build impact and needs to be documented. Furthermore, enabling various `CONFIG_SCHED_INSTRUMENTATION_*` options also impacts the build and runtime behavior. These need to be explained. * **Testing is inadequate:** The provided testing only shows the configuration changes, not the actual *results* of the testing. What were the observed problematic behaviors *before* the change? How do the logs *after* the change demonstrate that the issue is fixed? The provided diffs don't prove anything about functionality. The logs should showcase the issue and the resolution. Furthermore, testing only on `sim/nsh` with VFS instrumentation is likely insufficient. Ideally, testing should cover other scenarios where instrumentation might be used to ensure the fix doesn't introduce regressions elsewhere. Finally, the build host information is missing. **In short, the PR needs to provide more context, explain the impact thoroughly, and offer concrete evidence that the change works as intended.** -- 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-unsubscr...@nuttx.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
