تخطي للذهاب إلى المحتوى
القائمة
لقد تم الإبلاغ عن هذا السؤال
2 الردود
9303 أدوات العرض

I had one of the branches with testing enabled in Odoo.sh. I was trying to automatically set the company_id for customers in a multi-company setting. The functionality works fine.. however, looks like some of the tests around accounting are failing with the following: 


File "/home/odoo/src/odoo/odoo/models.py", line 3238, in check_access_rule
raise self.env['ir.rule']._make_access_error(operation, forbidden)
odoo.exceptions.AccessError: ('The requested operation ("read" on "Contact" (res.partner)) was rejected because of the following rules:\n- res.partner company\n\nNote: this might be a multi-company issue.\n\n(Records: company_1_data (id=358), User: Because I am accountman! (id=89))', None)

For some reason, due to those test errors, the build wasn't going anywhere and after 2 hours, it was dropped. 
My question is - is there a way to kill the build process right away so I can have it rebuilt with the new commits? I wasn't able to get the branch rebuilt with new commit while the previous build is still running. Thank you Odoo'ers. 

الصورة الرمزية
إهمال
الكاتب أفضل إجابة

Hi everyone - I realized that if the build is running too long due to errors in the tests, I can simply delete that branch, which apparently kills that build process as well. I can then check-in my fix and let the new build take over for that branch. So the delete-branch option looks like a reasonable option in this case. If you know a way of simply cancelling the build w/o nuke, let me know as well. Thanks! :-)

الصورة الرمزية
إهمال
أفضل إجابة

As a solution for the test env this is one of the solutions, but what if the build queued on the production env?

الصورة الرمزية
إهمال
المنشورات ذات الصلة الردود أدوات العرض النشاط
0
يونيو 19
3309
0
نوفمبر 21
1721
1
يوليو 25
1684
4
أبريل 25
12006
1
فبراير 25
3413