[bluez/bluez] 35fb23: doc: test-runner: document the virtual machine arc...

  Branch: refs/heads/1164802
  Home:   https://github.com/bluez/bluez
  Commit: 35fb236ce03cdfefd14c27cb63132ece2bd46f66
      https://github.com/bluez/bluez/commit/35fb236ce03cdfefd14c27cb63132ece2bd46f66
  Author: Luiz Augusto von Dentz [off-list ref]
  Date:   2026-09-14 (Mon, 14 Sep 2026)

  Changed paths:
    M doc/test-runner.rst

  Log Message:
  -----------
  doc: test-runner: document the virtual machine architecture

Add an ARCHITECTURE section describing how the virtual machine instance
is created and how it communicates with the launcher.

Document that the tool is both the launcher and the guest init, that
there is no disk image and the launcher root filesystem is shared
read-only over 9p, the TEST* variables passed on the kernel command
line, the sandbox mounts and the writable overlays needed on top of the
read-only root.

Also document the console and controller attachment: the guest console
is /dev/hvc0, and '-u' attaches the given socket as a second virtio
console, /dev/hvc1, on which the N_HCI line discipline is set so the
transport is HCI H:4 to the hci_uart driver. Mention '-o' as the way
additional channels are added, as done by test-functional.

While at it, add the missing '-H' and '-o' entries to OPTIONS.

Assisted-by: opencode:claude-opus-5


  Commit: fa99a412ac66e8f7a9a24df19c856b95df272b79
      https://github.com/bluez/bluez/commit/fa99a412ac66e8f7a9a24df19c856b95df272b79
  Author: Luiz Augusto von Dentz [off-list ref]
  Date:   2026-09-14 (Mon, 14 Sep 2026)

  Changed paths:
    M doc/test-functional.rst

  Log Message:
  -----------
  doc: test-functional: document the test environment architecture

Add an ARCHITECTURE section describing the split between the Pytest
upper tester, which runs on the developer machine and drives the test,
and the VM hosts started via test-runner, which run the BlueZ and kernel
instances under test.

Document the control, log, tty and shared channels set up on top of
test-runner and how they relate to the existing options, and the btvirt
and USB controller topologies. Details of the virtual machine setup
itself are left to test-runner, and writing VM-side test code to the
pytest-bluezenv documentation.

Also fix the temporary directory paths, which are named after
pytest-bluezenv rather than bluez-func-test.

Assisted-by: opencode:claude-opus-5


Compare: https://github.com/bluez/bluez/compare/35fb236ce03c%5E...fa99a412ac66

To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications