mirror of
https://github.com/odoo/runbot.git
synced 2025-03-19 09:25:46 +07:00
![]() Once more unto the breach, with the issue of pushing stagings (with "closes" annotations) to the target branch making GH close the PR & send the hook, which makes runbot_merge consider the PR closed and the staging cancelled. This probably still doesn't fix the issue, but it reduces the problematic window: before this, the process first updates the branches, then marks the PRs, then comments & closes the PRs, and finally commits the PR update. This means as runbot_merge is sending a comment & a status update to each PR in a staging, GH has some time to send the "closed" webhook behind its back, making the controller immediately cancel the current staging, especially if the v3 endpoint is a bit slow. By moving the commenting & closing out of the critical path (to the feedback queue), this window should be significantly shortened. |
||
---|---|---|
.. | ||
fake_github | ||
conftest.py | ||
local.py | ||
README.rst | ||
remote.py | ||
test_basic.py | ||
test_multirepo.py | ||
test_utils.py |
Execute this test suite using pytest. The default mode is to run tests locally using a mock github.com. See the docstring of remote.py for instructions to run against github "actual" (including remote-specific options) and the end of this file for a sample. Shared properties running tests, regardless of the github implementation: * test should be run from the root of the runbot repository providing the name of this module aka ``pytest runbot_merge`` or ``python -mpytest runbot_merge`` * a database name to use must be provided using ``--db``, the database should not exist beforehand * the addons path must be specified using ``--addons-path``, both "runbot" and the standard addons (odoo/addons) must be provided explicitly See pytest's documentation for other options, I would recommend ``-rXs``, ``-v`` and ``--showlocals``. When running "remote" tests as they take a very long time (hours) ``-x`` (aka ``--maxfail=1``) and ``--ff`` (run previously failed first) is also recommended unless e.g. you run the tests overnight. ``pytest.ini`` sample --------------------- .. code:: ini [github] owner = test-org token = aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa [role_reviewer] name = Dick Bong user = loginb token = bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb [role_self_reviewer] name = Fanny Chmelar user = loginc token = cccccccccccccccccccccccccccccccccccccccc [role_other] name = Harry Baals user = logind token = dddddddddddddddddddddddddddddddddddddddd