-
-
Notifications
You must be signed in to change notification settings - Fork 93
runbot_travis2docker: does not seem to work on OCA runbot #105
Comments
@moylop260 your feedback is very welcome on this. Thanks for your help. |
What is your |
The Travis file needs to be upgraded to the new version. This error is saying there is no "TESTS=1" in the matrix, which is defaulted so doesn't hurt Travis. Happens all the time on our instance, which is why you see me submitting new Travis files quite often. You can see the transition on our web repo. Skipped are all before merge of OCA/web#447 or OCA/web#448 Although @moylop260 comment maybe alludes to this being fixed in a newer T2D version? |
@gurneyalex It's building here: I don't see the url in the image of your first comment but could change it by: NOTE: The docker version is too old this could get new errors by old bug but Its is other matter. |
@lasley For this case we are using a |
Yup that Travis should definitely not be exhibiting this issue 😦 |
|
@gurneyalex |
@gurneyalex
Right? |
@moylop260 I think the problem comes from gurneyalex/odoo-extra@92b578a which is installed on our instance : the screenshot shows the configured URL (without the https:// prefix which is added by that patch, and your addon expects a full URL. |
@gurneyalex Thanks for the information |
@moylop260 things seem to be better, cf. |
@moylop260 at lease 1 build worked. Are the failures on the other branches expected ? |
Yeah, we have currently the following issue Showing in travis too the same error: Then it is not a runbot or travis2docker error. It is a MQT expected fail. IMHO we are ready (We don't have real projects installing just base) |
We could use a "technical" real repository like as server-tools I'm testing it from custom instance using all the patches and It is working fine: |
Yesterday I enabled docker builds for
|
I just enabled
For now all of them have the tests disabled (same for rma and server-tools). |
Hmmm looks like the new version isn't appending the log to DB. I admittedly haven't updated my Runbot since before the code sprint, so I haven't functionally tested our improvements outside of local. I'll update today and see what's wrong. |
Fix is in #107 - seems my PEP8ing after test and before PR ended up changing the end result of the |
To see the logs we need a How are you checking this issue? |
I found a warning in a runbot build but is not enabled for docker. @gurneyalex |
added
|
I saw in stock-* project the following error (and fix): OCA/maintainer-quality-tools#386 |
I saw in l10n-switzerland project the following error (and fix): Vauxoo/docker-odoo-image@3eaae03
|
Fixed from #109 |
Gotta love the edge cases that crop up when launching at scale 😉 |
@gurneyalex - We made some changes that will resolve the issues we've been seeing. Edit: it may only be this issue now that I think about it Would you mind doing a We'll also need to update the runbot addon to the new version merged in #109. |
I'm sorry I can't today. I'll try hard tomorrow. |
@lasley @moylop260 I've just updated the runbot as requested |
Thank you |
@moylop260 I did this. Running 99680477d329aee2e54b9cf512531479cd118920 (which is on 3.0.8). |
maybe I'm catching an outdated version. Can you make a 3.0.8 release and publish it on pypi ? It's way easier for me due to the way the runbot is deployed to use published documented versions rather than github heads. |
I'll do it |
Someone is wrong |
With the following environment:
~/runbot-addons (9.0-OCA-installation)$ git log -r -2
commit 33e5a2abb43cbd24b738d79d18964de7c3f17997
Merge: 251dc63 092e6f8
Author: Alexandre Fayolle <[email protected]>
Date: Wed Nov 23 15:01:53 2016 +0100
Merge remote-tracking branch 'origin/9.0' into 9.0-OCA-installation
commit 092e6f889b252f82cc2abd1bfb87f6443a37bf5b
Merge: 8044166 b0a5635
Author: Pedro M. Baeza <[email protected]>
Date: Mon Nov 21 18:30:03 2016 +0100
Merge pull request #109 from vauxoo-dev/9.0-oca-pull-img-moy
[REF] runbot_travis2docker: Auto pull image for long-term updates
pip install --upgrade travis2docker==3.0.9
travisfile2dockerfile --version
travisfile2dockerfile 3.0.9
Do you have a logger error? |
@gurneyalex The |
@gurneyalex Tell me if I can help... |
I'm sorry I was away yesterday. I just updated the runbot. I'll monitor carefully the builds in the coming hours |
@moylop260 Things seem to be a bit better. My build on OCA/web#498 was correctly processed. |
@gurneyalex - I rebuilt all of the website builds that were skipped, and we seem good to go. And in even better news, OCA/website#284 now works so that means the RVM install is working too! |
I rebuilt https://runbot.odoo-community.org/runbot/build/3273461 and now is working
I rebuilt https://runbot.odoo-community.org/runbot/build/3273217 and now is working |
@gurneyalex |
@moylop260 I just enabled travis2docker on all projects. |
I probably got some configuration wrong.
I'm using docker 1.6.2 (from jessie-backports), the user running odoo is a member of the docker group (but odoo is not running inside docker).
Test repository is https://runbot.odoo-community.org/runbot/repo/github-com-vauxoo-dev-runbot-branch-remote-name-grp-feature2-232
Setup:
I get empty builds or skipped builds,
docker ps
says nothing, anddocker images
is also empty.Weird line in the logs:
The text was updated successfully, but these errors were encountered: