odoo/upgrade#8239
Created by Upgrade, Christophe Simonis (chs)
Statuses:
- ci/runbot: Test upgrades between stable versions
- ci/upgrade_enterprise: Test upgrades for enterprise master
- label
- odoo-dev:master-imp_snippets_prepare_py_3_14-cawo
- head
- a2c7e6b21033f5dc19a730f4a2c8365d7f858a9e
- merged
- 3 weeks ago by Upgrade, Christophe Simonis (chs)
| odoo/upgrade | odoo/upgrade-util | |
|---|---|---|
| master | #8239 | #294 |
[FIX] */16.0+: correct usage of ProcessPoolExecutor
Force the max_workers and mp_context of the ProcessPoolExecutor. Since python 3.8, the mp_context needs to be forced to "fork" on macOS.
See also odoo/upgrade-util#294
> Warning Please follow and check the relevant boxes for your PR, otherwise the review may take longer.
For a PR that adds a new upgrade script (for the Odoo's master branch or one of the RR versions):
- [ ] I've added the references to the Enterprise and/or Community PRs in the commit message, even if they are already merged.
- [ ] I've added an overall description of the changes made in the Community/Enterprise branches.
For a PR that fixes an issue on an already existing upgrade script:
- [ ] I've added a clear description of the issue including information on how to reproduce it.
- [ ] I've tested the fix and included references of upgrade requests where this fix will be applicable in the form of upg-<request_number>.
- [ ] I've included references to the OPW, if applicable, in the form of opw-<ticket_number>.
- [ ] I've tested this fix on other DBs, not just the ones with the issue.
For all PRs:
- [ ] My commit's title follows the right format.
- [ ] My commit's body includes information about the changes.
- [ ] I've added odoo/upgrade as a reviewer.
- [ ] I've read and understood this list.
- [x] I will ensure all the CI checks are green.
> Note More info can be found in the wiki.