[RFC] enable sof-test on ChromeOS

[aiChaoSONG]

I can make sof-test/test-case/check-playback.sh run on ChromeOS, but there are some issues. terminal.txt

1. the visudo configuration seems only takes effect once.
2. there is no /var/log/kern.log file.
3. the sudo funciton in hijack.sh report a library issue, but the file does exist on the system.

   dmesg: error while loading shared libraries: libtinfow.so.6: cannot open shared object file: No such file or directory

4. no sudo group on ChromeOS
5. we have to specify bash or python3 when run shell/python scripts, check https://chromium.googlesource.com/chromiumos/docs/+/master/security/noexec_shell_scripts.md
6. journalctl require root permission

How dependencies are installed?

• I found a package management tool named chromebrew, this tool can help to install dependencies as apt did for us.
• python3 dependencies should be installed with pip3
• this tool can not run with root.

[marc-hb]

https://pip.pypa.io/en/stable/installing/#installing-with-get-pip-py instead of chromebrew?

Running everything as root should avoid sudo, at least to get things started.

[fredoh9]

For python problems, installing miniconda is the solution. It will take care of python version and packages. I will summarize the procedures.

Need package manager, I found chromebrew useful. expect, graphviz pacakage can be installed https://medium.com/@dihuta/chromebrew-crew-chromeos-package-manager-a91e56a3d898

wget -q -O - https://raw.github.com/skycocker/chromebrew/master/install.sh | bash

Need to remount to add executable permission.

sudo mount -o remount exec /home
sudo mount -o remount exec /home/chronos
sudo mount -o remount exec /home/chronos/user

/var/log/kern.log error, I just did touch /var/log/kern.log but need to be fixed.

sof-logger is not found. Need to look for same version with current SOF binary

/etc/sof is missing, hence sof-{PLATFORM}.ldc is missing. need to find matching file with current SOF binary

[fredoh9]

for miniconda, there is a shell script installer.

curl -O https://repo.anaconda.com/miniconda/Miniconda3-latest-Linux-x86_64.sh
bash "./Miniconda3-latest-Linux-x86_64.sh" -b -p /usr/local/miniconda3

#setup conda env
#export PATH="/usr/local/miniconda3/bin:$PATH"
. /usr/local/miniconda3/etc/profile.d/conda.sh

conda -V
conda init

conda update conda -y
conda create -y -n sof-test python=3.7
conda activate sof-test
pip install -r "$PATH_SOF/requirement.txt"

[fredoh9]

I'm using CML Chromebook for reference ChromeOS platform, version R89-13729.1.0, dev image. Without ChromeBrew or minicodna, default python is python 3.6.5. get-pip.py works fine! pip version today i have is pip 20.3.3. I'm able to run check-playback.sh

graphviz and numpy installed fine but scipy couldn't be installed due to unknown error.

[marc-hb]

https://pexpect.readthedocs.io/en/stable/

Pexpect is in the spirit of Don Libes’ Expect, but Pexpect is pure Python. Unlike other Expect-like modules for Python, Pexpect does not require TCL or Expect nor does it require C extensions to be compiled. It should work on any platform that supports the standard Python pty module

[marc-hb]

How to turn a Chromebook device into SOF (on Zephyr) development with Crouton by @andyross https://github.com/zephyrproject-rtos/zephyr/pull/36528/commits/16456d475f4354005cb656f4d5e975ec5b098696

[marc-hb]

How to turn a Chromebook device into SOF (on Zephyr) development with Crouton by @andyross zephyrproject-rtos/zephyr@16456d4

This was merged some time ago in https://github.com/zephyrproject-rtos/zephyr/pull/37647

I'm listing Crouton and other Linux-on-Chromebooks options in new https://github.com/thesofproject/sof-docs/pull/379

[plbossart]

Can we close this @aiChaoSONG ?

[aiChaoSONG]

If download sof-test to /usr/local, and install dependencies with chromebrew, sof-test can run on ChromeOS

[marc-hb]

For convenience: https://thesofproject.github.io/latest/getting_started/intel_debug/introduction.html#chromebooks-and-sof

[marc-hb]

I just looked at a recent ChromeOS image developer image (less than a few weeks old) to collect some "datapoints" relevant for sof-test and it looks like none of these has changed in the last few years:

• No journalctl, still the same old rsyslogd. EDIT: except for a short time around 2020, see below. So in sof-test calls to journalctl -k would have to be replaced by something like grep ' kernel: ' /var/log/messages with the huge caveat that journalctl --since test_start_time and journalctl --boot 0 would have to be re-implemented. /var/log/messages has not just the current boot but ALL boots until the last time /var/log/messages was log-rotated! In the past we had some awkard / buggy DMESG_LOG_START_LINE but it was joyfully deleted when moving to journalctl (see 18c7e6155053b and others). Time warps could also become much more "fun" https://github.com/thesofproject/sof-test/discussions/908

• No systemctl, still using upstart that Ubuntu sponsored but abandoned. From https://upstart.ubuntu.com/

  Upstart Project is in maintenance mode only. No new features are being developed and the general advice would be to move over to another minimal init system or systemd.

• cras is still the ALSA daemon

• As mentioned by @andyross in https://github.com/zephyrproject-rtos/zephyr/pull/50424#issuecomment-1253150425, I can confirm python is present but still stuck to obsolete version 3.6

cc:

• https://github.com/thesofproject/linux/issues/3867
• https://github.com/thesofproject/sof-test/issues/292
• https://github.com/thesofproject/sof-test/pull/649
• https://github.com/thesofproject/sof-test/pull/684
• sudo journalctl for chrome compatibility https://github.com/thesofproject/sof-test/commit/76e90c35778c6f ??
• https://bugs.chromium.org/p/chromium/issues/detail?id=583671 systemd in ChromeOS - last update in 2018

[aiChaoSONG]

An intern from Chrome team asked for help to migrate sof-test to chrome OS, I think it is done, but unfortunately she doesn't upstream anything. there is no journalctl on chrome, but there is an alternative tool craslog, which provide similar options to journalctl.

[marc-hb]

Thanks @aiChaoSONG for pointing me to http://crbug.com/1066706 "removing journald" and other useful links. Apparently ChromeOS used journalctl for a short timespan, only 1 or 2 years around 2020 and then went back to .log text files.

It's not easy to find information because the design documents like go/improve-cros-logging seem closed-source but looking at some source code and git logs it seems chromeOS now provides a croslog wrapper on top of rsyslogd that provides features that were lost when removing journalctl like for instance journalctl --boot and the ability to interleave / multiplex logs from different rsyslogd text files. This croslog front-end looks like it also provides (provided?) journalctl compatibility during the transition.

tl;dr: sof-test should very likely rely on croslog when run on ChromeOS. @aiChaoSONG I guess craslog was a typo for croslog?

https://chromium.googlesource.com/chromiumos/third_party/autotest/+/b1ec0cb83b2feb1b https://chromium.googlesource.com/chromiumos/platform2/+/3417bf876ad9c88f79c3ddfe569c3fbb32616896 https://docs.google.com/document/d/1xbC-A4zgEIzaCU6SS-XI7QiF3XjEQB5_4uw2XCqcw9M/edit#heading=h.qapfgw2vziay

[kv2019i]

I was not aware of this ticket (but now I am, thanks @marc-hb ). I did a test with R106 based image and results I got: Tested sof-test today on recent CrOS and...

• it partially works - you can run many of the tests
• error reporting is not working as there is no journalctl
  • tried a quick hack to support basic "plain dmesg" but seems this would need more time get working
• suspend cases don't work as rtcwake does not work as in desktop distros (powerd_dbus_suspend is the more used tool for this in cros -- based on what tool is used in bug reports when suspend related issues are found)

Seems to be aligned to what has been already discussed on this ticket. The rtcwake issue might require more study, whether this is a configuration issue specific to my board/kernel, or something that will be hit more generally on CrOS.