Boot device for presubmit testing #463
Conversation
jemoreira
requested review from
Databean,
rmuthiah,
jmacnak and
adelva1984
as code owners
jemoreira
force-pushed
the
main
branch
2 times, most recently
from
187005a to
b4abe4b
Compare
| ls -l /dev/"${d}" | ||
| sudo chmod a+rw /dev/"${d}" | ||
| done | ||
| } |
There was a problem hiding this comment.
Is this still necessary with sudo -u testrunner "${TOOL_DIR}/runtests.sh" ... in the presubmit.sh script?
The other tests no longer validate the group permissions are correct if everything can access these devices.
There was a problem hiding this comment.
Failed without it. Those devices are owned by root:root, I either had to change the group or give permissions to all.
There was a problem hiding this comment.
This could be because the new udev rules defined in our debian packages haven't been applied so they don't trigger on the new /dev files introduced by installing the kernel modules.
Does refreshing the udev rules help with this?
There was a problem hiding this comment.
Tried that and it still fails with
0: failed to open virtual socket device /dev/vhost-vsock
1: Permission denied (os error 13)
26aeb95 to
06aa798
Compare
The meson version in ubuntu20.04 doesn't have the compile subcommand, it expects instead for the builder (ninja) to be called directly.
includes testing aosp-main phone x86_64
Fetches from android build api with
cvd fetchLaunches devices with
launch_cvd(cvd start coming soon).Tests only aosp-main/aosp_cf_x86_64_phone-trunk_staging-userdebug for now.