odoo-sh

Hello, yes, the module is installed as you can see in runtest.log We are executing pytest at first followed by odoo --test-enable. [runtests.log](https://github.com/camptocamp/pytest-odoo/files/8159941/runtests.log) UPDATE: the run test with standard odoo...

yes. we did import our testfile in `tests/__init__.py` odoo -d xxx -i $mod_name --stop-after-init --test-enable succeed. As a workaround we changed the following and it worked. ``` Commented line 122:...

yes tiny_apps is a folder. we have `addons_path=... , /odoo/src/tiny_apps/tiny_apps, .....` tiny_apps folder has many modules with test. We want to run pytest for selective modules.

For me.. snap remove --purge microk8s snap install microk8s --classic --channel=1.29/stable. root@microk8s-master:~# microk8s status microk8s is not running. Use microk8s inspect for a deeper inspection. The inspect log looks same...

``` root@microk8s-master:~# microk8s start root@microk8s-master:~# microk8s status microk8s is not running. Use microk8s inspect for a deeper inspection. root@microk8s-master:~# microk8s inspect Inspecting system Inspecting Certificates Inspecting services Service snap.microk8s.daemon-cluster-agent is...

+1. I have same issue. Hoping for someone with java knowledge to update the client API.

For those having the issue with docker version > 25, please check this [thread](https://stackoverflow.com/questions/37242217/access-docker-container-from-host-using-containers-name) of fnkr. This is an ideal alternative. Thanks,

@pedrobaeza sorry for the trouble and thanks for the comments. I think we are going to follow your advice and start using individual account, it seemed easier when we started....