跳至內容
選單
此問題已被標幟
2 回覆
9304 瀏覽次數

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
6月 19
3309
0
11月 21
1722
1
7月 25
1685
4
4月 25
12011
1
2月 25
3414