mirror of
https://github.com/odoo/runbot.git
synced 2025-03-19 09:25:46 +07:00
![]() Normally, two PRs from the same owner with the same branch name (source) are batched together, and that's represented by batching them by label e.g. two PRs labelled `odoo-dev:12.0-snailmail-address-format-anp` means they probably should be merged together somehow. *However* this is an issue when editing via the web interface: if the editor doesn't have write access to the repository, github automatically createa a branch called `patch-<n>` under their ownership, where `<n>` is a sequence (of sorts?) *within the user's fork*. This means it's possible (and indeed easy) to create <foo>:patch-1 on different (non-forks) but related repositories without them actually being co-dependent, at which point they get blocked on one another, which can lead to them being blocked (period) due to runbot not currently handling co-dependencies between PRs. |
||
---|---|---|
.. | ||
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