busybox: enable testcase logging

[mateusz-bloch]

JIRA: CI-384

Description

Motivation and Context

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

How Has This Been Tested?

• Already covered by automatic testing.
• New test added: (add PR link here).
• Tested by hand on: (list targets here).

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing linter checks and tests passed.
• My changes generate no new compilation warnings for any of the targets.

Special treatment

• This PR needs additional PRs to work (list the PRs, preferably in merge-order).
• I will merge this PR by myself when appropriate.

[github-actions]

Unit Test Results

5 957 tests  +334   5 316 ✔️ +316   30m 42s ⏱️ + 3m 24s
   333 suites +  35      641 💤 +  19 
       1 files   ±    0          0 ❌  -     1 

Results for commit 3ba316c. ± Comparison against base commit 9feddd4.

This pull request removes 1 and adds 335 tests. Note that renamed tests count towards both.

phoenix-rtos-tests/libc/misc ‑ armv7m4-stm32l4x6-nucleo:phoenix-rtos-tests/libc/misc

flash ‑ riscv64-generic-qemu:flash
phoenix-rtos-tests/libc/exit ‑ armv7a7-imx6ull-evk:phoenix-rtos-tests/libc/exit.stdlib_exit.atexit_few_calls
phoenix-rtos-tests/libc/exit ‑ armv7a7-imx6ull-evk:phoenix-rtos-tests/libc/exit.stdlib_exit.atexit_register_inside
phoenix-rtos-tests/libc/exit ‑ armv7a7-imx6ull-evk:phoenix-rtos-tests/libc/exit.stdlib_exit.atexit_two_nodes
phoenix-rtos-tests/libc/exit ‑ armv7a7-imx6ull-evk:phoenix-rtos-tests/libc/exit.stdlib_exit.stream_flush
phoenix-rtos-tests/libc/exit ‑ armv7a7-imx6ull-evk:phoenix-rtos-tests/libc/exit.unistd_Exit.SIGCHLD_sent
phoenix-rtos-tests/libc/exit ‑ armv7a7-imx6ull-evk:phoenix-rtos-tests/libc/exit.unistd_Exit.chk_if_exits
phoenix-rtos-tests/libc/exit ‑ armv7a7-imx6ull-evk:phoenix-rtos-tests/libc/exit.unistd_Exit.close_streams
phoenix-rtos-tests/libc/exit ‑ armv7a7-imx6ull-evk:phoenix-rtos-tests/libc/exit.unistd_Exit.exit_status_waitpid
phoenix-rtos-tests/libc/exit ‑ armv7a7-imx6ull-evk:phoenix-rtos-tests/libc/exit.unistd_Exit.new_parent_id
…

♻️ This comment has been updated with latest results.

[damianloew]

It seems that there are also other places where test cases start:

There you also don't know when you should start parsing output.

Please correct it, run all the tests and make sure that all the output is formatted correctly.

[mateusz-bloch]

Right, it turns out that in the new style of BusyBox tests, some may include checks within the test itself. Currently, this is only the case for bunzip2.tests and bzcat.tests.

After the recent changes:

[damianloew]

Thanks, one more nitpick: maybe it would be good to do ---Testcase 'testcase name' starting---

[mateusz-bloch]

Did you mean that?

[damianloew]

Isn't it the same?

[mateusz-bloch]

Is that what it was about?:

I didn't understand, previously I changed only that the testcase was printed and not the entire path in one case of printning logs.

[damianloew]

Yeah, exactly