Pular para o conteúdo
Esta pergunta foi sinalizada
testsodoo.shv15
3 Respostas
4952 Visualizações
Avatar
Ken Hawley

While attempting to rebuild instance with new module added, the install log has the following:

2023-03-15 15:34:31,359 4 INFO xxxxx-from-master-7610128 odoo.service.server: 937 post-tests in 2567.13s, 997354 queries
2023-03-15 15:34:31,359 4 ERROR xxxxx-from-master-7610128 odoo.tests.runner: 0 failed, 1 error(s) of 2517 tests when loading database 'xxxxx-from-master-7610128'
2023-03-15 15:34:31,363 4 INFO xxxxxx-from-master-7610128 odoo.service.server: Initiating shutdown
2023-03-15 15:34:31,363 4 INFO xxxxx-from-master-7610128 odoo.service.server: Hit CTRL-C again or send a second signal to force the shutdown.
2023-03-15 15:34:31,865 4 INFO xxxxx-from-master-7610128 odoo.sql_db: ConnectionPool(used=0/count=0/max=16): Closed 5 connections
odoo-bin process returned error code 1. Please check install.log 

If zero tests failed, yet there was an error, what is the error?  It is certainly not in the install.log.  Is there some other place errors are logged by the tests?

This is in a development branch that has been cloned down from our master that runs fine absent this module.


Avatar
Cancelar
Ken Hawley
Autor

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.

Ken Hawley
Autor

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?

Avatar
Ken Hawley
Autor Melhor resposta

Still very frustrating, but I was eventually able to capture a log that allowed me to find the problem.

Avatar
Cancelar
Avatar
Fredric
Melhor resposta

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

Avatar
Cancelar
Avatar
Dustin Walton
Melhor resposta

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

Avatar
Cancelar
Dustin Walton

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

Publicações relacionadas Respostas Visualizações Atividade
How can I delete an Odoo.sh project completely? Resolvido
odoo.sh v15
Avatar
Avatar
Avatar
3
jul. 24
7463
Odoo sh won't let me update the current module, the update current module button is gray
odoo.sh v15
Avatar
Avatar
1
dez. 22
4189
Initiating shutdown
odoo.sh v15
Avatar
0
out. 22
3297
Odoo.sh build testing failing due to custom python constraint. How can I fix?
constraints tests odoo.sh
Avatar
0
mar. 21
4320
Odoo.sh test sporadically fail with Can't load service 'localization' because: TypeError: Failed to fetch (odoo 16)
javascript tests odoo.sh 16.0
Avatar
Avatar
1
out. 24
2562