Still very frustrating, but I was eventually able to capture a log that allowed me to find the problem.
0
Odoo.sh v.15 Tests failed "Please check install log." Nothing in the install log aside from the message shown.
3 答案
0
最佳答案
I ran into a similar issue a while back—"Test Failed" showing even though everything seemed to be working fine on the surface. In my case, it turned out the test error was triggered by an unhandled exception inside a related dependency that wasn’t even part of the module I was updating. Odoo.sh can sometimes be unclear with how it logs those. If you're just looking to rule things out, try isolating that module in a clean build with all logging levels enabled (including --log-level=test) to catch anything that might slip by.
Also random side note while digging through logs this morning—I took a short break and came across this fun little word puzzle game: 1word4pics.com
0
最佳答案
1. Try this code in odoo.conf file
addons-path=path.../addons,path..../custom-addonsExample:addons_path = /home/cybrosys/odoo-17.0/addons,/home/cybrosys/odoo-17.0/custom_app
2. Add Parameters ; -c odoo.conf -u custom_module_name
1
备注
odoo
-
My module is installed, and the different components from the models in the module are in their proper places, even if the "Branches" display indicates "Test Failed" when I connect to it. https://slice-master.io
I guess I should note that I am running with the settings:
Install only my modules (does not include submodules)
Validate the test suite on new builds.
Presumably, I could disable the test suite, but that doesn't seem like a good idea.
Well that's interesting. Even though the "Branches" display comes up and says "Test Failed", I can still connect to it and my module is installed and the various elements from the models in the module are in place.
Could it be the problem is in the Odoo.sh interface and no tests have actually failed?