| Message ID | 20250212135209.129361-1-arkadiusz.bokowy@gmail.com (mailing list archive) |
|---|---|
| State | Accepted |
| Commit | 571bc32fd9d0679e22e6194ce2877bcabc97a762 |
| Headers | show |
| Series | [1/4] test-runner: Increase amount of RAM available in VM | expand |
| Context | Check | Description |
|---|---|---|
| tedd_an/pre-ci_am | success | Success |
| tedd_an/BuildEll | success | Build ELL PASS |
| tedd_an/BluezMake | success | Bluez Make PASS |
| tedd_an/MakeCheck | success | Bluez Make Check PASS |
| tedd_an/MakeDistcheck | success | Make Distcheck PASS |
| tedd_an/CheckValgrind | success | Check Valgrind PASS |
| tedd_an/CheckSmatch | success | CheckSparse PASS |
| tedd_an/bluezmakeextell | success | Make External ELL PASS |
| tedd_an/ScanBuild | success | Scan Build PASS |
This is automated email and please do not reply to this email! Dear submitter, Thank you for submitting the patches to the linux bluetooth mailing list. This is a CI test results with your patch series: PW Link:https://patchwork.kernel.org/project/bluetooth/list/?series=933153 ---Test result--- Test Summary: CheckPatch PENDING 0.21 seconds GitLint PENDING 0.20 seconds BuildEll PASS 20.82 seconds BluezMake PASS 1547.50 seconds MakeCheck PASS 13.73 seconds MakeDistcheck PASS 161.08 seconds CheckValgrind PASS 217.41 seconds CheckSmatch PASS 295.20 seconds bluezmakeextell PASS 97.85 seconds IncrementalBuild PENDING 0.32 seconds ScanBuild PASS 862.48 seconds Details ############################## Test: CheckPatch - PENDING Desc: Run checkpatch.pl script Output: ############################## Test: GitLint - PENDING Desc: Run gitlint Output: ############################## Test: IncrementalBuild - PENDING Desc: Incremental build with the patches in the series Output: --- Regards, Linux Bluetooth
Hello: This series was applied to bluetooth/bluez.git (master) by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>: On Wed, 12 Feb 2025 14:52:06 +0100 you wrote: > When using default kernel configuration from Ubuntu 24.04 patched with > the configuration from tester.config, the kernel image is too big to run > on 192M bytes of RAM. As a result the test-runner exits without any > message (because of the "quite" kernel command line option). > --- > tools/test-runner.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) Here is the summary with links: - [1/4] test-runner: Increase amount of RAM available in VM https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=571bc32fd9d0 - [2/4] test-runner: Remove the "-nographic" option passed to QEMU https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=8e76a4d0dc56 - [3/4] test-runner: Do not use short-form of readonly option https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=54210e0210d4 - [4/4] test-runner: Use host CPU when starting VM https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=4577f50e739f You are awesome, thank you!
diff --git a/tools/test-runner.c b/tools/test-runner.c index cd8b86d7a..77c89f3f9 100644 --- a/tools/test-runner.c +++ b/tools/test-runner.c @@ -211,7 +211,7 @@ static char *const qemu_argv[] = { "-monitor", "none", "-display", "none", "-machine", "type=q35,accel=kvm:tcg", - "-m", "192M", + "-m", "256M", "-nographic", "-net", "none", "-no-reboot",