support OEQA inside container
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest4 patches 0 repliesNew
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | oeqa/utils/httpserver: allow to pass in listening portmeta/ | +2 | 0 replies | |
| 2/4 | oeqa/runtime/context.py: support listening port in TEST_SERVER_IPmeta/ | +6 | 0 replies | |
| 3/4 | oeqa/target/ssh oeqa/target/qemu: expose server listening port to testsmeta/ meta/ | +3 | 0 replies | |
| 4/4 | oeqa/runtime/apt dnf opkg: support running from within docker containermeta/ meta/ meta/ | +8 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/4] support OEQA inside container
Hi,
With these patches it is possible to run bitbake inside a docker container and still successfully execute the OEQA tests that require the target to talk to a temporary http server spawned on the machine running bitake, e.g. using crops.
This wasn't possible so far because:
* we need to map a port from outside the container into the container for the target to be able to reach the http server
* we need to pass the IP address of the docker host to the target, e.g. in the OPKG repository URL, but we can't bind the http server to that IP address, as the http server is running inside the container with a different IP address - the bind would fail
To make this work, TEST_SERVER_IP needs to be set to the IP address of the docker host, and the port that is mapped into the container can now also be specified in TEST_SERVER_IP, similar to TEST_TARGET_IP
Cheers,
Andre'