fs cases: fix compile error

[xiaoxiang781216]

Summary

kernel/fs/cases/fs_stream_test.c:279:70: error: format ‘%zi’ expects argument of type ‘signed size_t’, but argument 4 has type ‘int’ [-Werror=format=]
  279 |           syslog(LOG_ERR, "len = %zi != return value from fwrite = %zi",
      |                                                                    ~~^
      |                                                                      |
      |                                                                      long int
      |                                                                    %i
  280 |                  len, ret);
      |                       ~~~
      |                       |
      |                       int
kernel/fs/cases/fs_stream_test.c:311:69: error: format ‘%zi’ expects argument of type ‘signed size_t’, but argument 4 has type ‘int’ [-Werror=format=]
  311 |           syslog(LOG_ERR, "len = %zi != return value from fread = %zi",
      |                                                                   ~~^
      |                                                                     |
      |                                                                     long int
      |                                                                   %i
  312 |                  len, ret);
      |                       ~~~
      |                       |
      |                       int

Impact

fix compiler warning

Testing

ci

[nuttxpr]

[Experimental Bot, please feedback here]

Yes, this PR likely meets the NuttX requirements, though it could be slightly improved.

Strengths:

• Clear Summary: The summary identifies the problem (compiler warnings related to format specifiers) and the affected file. The error messages themselves are helpful context.
• Concise Impact: Clearly states the impact is fixing a compiler warning.
• Testing Indication: "ci" suggests Continuous Integration testing was performed, which is generally good.

Weaknesses/Areas for Improvement:

• Missing Details in Summary: While the error messages are present, a brief explanation of why the change was made (e.g., "Incorrect format specifier %zi used for int type, changed to %i") would enhance clarity.
• Vague Testing: "ci" is insufficient. While CI is good, the PR should specify:
  • Build Host(s): The CI environment details (OS, compiler, etc.) are missing.
  • Target(s): Which architectures/boards were tested in CI?
  • Logs (or their absence): Ideally, relevant snippets of the CI logs (before and after) showing the warning disappearing should be included. If the logs are excessively long, a statement like "CI logs show successful compilation without the mentioned warnings on [list of architectures]" would suffice.

Recommendation:

Add the missing details mentioned above, especially the testing information. While the PR is likely acceptable as-is, providing more context will make it easier for reviewers to understand and approve the change.

[cederom]

Thank you @xiaoxiang781216 :-)

[tmedicci]

Thanks, @xiaoxiang781216 !