Failing tests with Odoo 9.0

[ruiztulio]

I have a repo in git.vauxoo.com and it uses odoo-shippable image to execute the tests it was green until the image was updated, the checking the logs I realized that for some reason it was using odoo 8.0 instead of 9.0 (the few lasts lines):

And in the previous one (the is from yesterday):

We didn't change the tests nor the code because we're testing the CI system.

Also we notice this:

Compared with the one that was successfully tested:

Regards

[moylop260]

@LuisAlejandro The issue is with odoo cache process.

We need execute before a fetch to download the required branch.

Could you help us?

[LuisAlejandro]

Ok, i'll take a look! On Jun 24, 2016 4:02 PM, "moylop260" notifications@github.com wrote:

@LuisAlejandro https://github.com/LuisAlejandro The issue is with odoo cache process.

We need execute before a fetch to download the required branch.

Could you help us?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Vauxoo/docker-odoo-image/issues/135#issuecomment-228448514, or mute the thread https://github.com/notifications/unsubscribe/AAT0SxgI236uSofaAM0BgXPVUQKBpSNWks5qPDfjgaJpZM4I-E-G .

[LuisAlejandro]

@ruiztulio why do we use an 8.0 image to test 9.0 code?

[moylop260]

@luisAlejandro

The image odoo-shippable is for all odoo versions. I use this image to run t2d for other no-odoo projects.

This image is similar to https://quay.io/repository/travisci/travis-python

[ruiztulio]

@LuisAlejandro as @moylop260 said we use a single image and I repeat what I said here if you're going to change something at least you have to do it in the top of the previous state, that is, if it was working properly with the 9.0 or the "wired" app versions so it have to continue working that way and then, in a later stage, if you consider that we should use separate test images for every Odoo version, change some package versions or you have any other idea it can be discussed, decided and planned as we see it fit.

ATM we need this image working properly as it was.

Regards.

[LuisAlejandro]

Cool, I'll be changing it ASAP. I apologize for this error, I still have things to learn about our architecture so that i don't miss anything. Regards.

[moylop260]

@LuisAlejandro Do you have any news?

[LuisAlejandro]

Sorry, no @moylop260. Tomorrow i'll give it a look.

On Tue, Jul 5, 2016 at 1:11 PM, moylop260 notifications@github.com wrote:

@LuisAlejandro https://github.com/LuisAlejandro Do you have any news?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Vauxoo/docker-odoo-image/issues/135#issuecomment-230541104, or mute the thread https://github.com/notifications/unsubscribe/AAT0Swr_kaiEJooUNC_U_iI8xp3jauM-ks5qSpBSgaJpZM4I-E-G .

[moylop260]

@KarenKawaii Could you help us to fix this too late issue?

[KarenKawaii]

Roger that @moylop260 I 'll put up with the information of this issue.

[moylop260]

@KarenKawaii I think that you should looking for here: MQT/travis/travis_install_nightly#L43-L53

[KarenKawaii]

Thanks for the tip

El jul. 22, 2016 2:35 PM, "moylop260" notifications@github.com escribió:

@KarenKawaii https://github.com/KarenKawaii I think that you should start looking for here: MQT/travis/travis_install_nightly#L43-L53 https://github.com/Vauxoo/maintainer-quality-tools/blob/824b2fa737ccffc067db1787eac63cb47d4af586/travis/travis_install_nightly#L43-L53

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Vauxoo/docker-odoo-image/issues/135#issuecomment-234635938, or mute the thread https://github.com/notifications/unsubscribe-auth/ALMoyFWSgmJQ-hAZl0ZQTbhp7wRnUa10ks5qYRuBgaJpZM4I-E-G .