[New-bugs-announce] [issue36215] Should AppVeyor run compile Python in debug mode?

[STINNER Victor]

New submission from STINNER Victor <vstinner at redhat.com>:

The Windows buildbots have been broken by PR 12073. Problem: AppVeyor didn't catch the bug before the change has been merged. Why? Because AppVeyor builds Python in release mode, whereas Windows buildbots build Python in debug mode.

https://bugs.python.org/issue36139#msg337320

IMHO AppVeyor should also build Python in debug mode to catch most bugs.

We should compare build time in debug mode and in release mode to see the cost of debug mode.

---

Somehow related issue: AppVeyor and Travis CI tests passed on PR 10497 "bpo-35224: PEP 572 Implementation" but buildbots failed. The problem is that buildbots pass "-u all" to "python -m test", whereas pre-commit CIs use "-uall,-cpu" (.travis.yml) or "-uall -u-cpu -u-largefile" (.github/appveyor.yml).

https://github.com/python/cpython/pull/10497#issuecomment-457409029

---

It's a trade-off between preventing bugs and CI performance...

----------
components: Build
messages: 337335
nosy: pablogsal, vstinner, zach.ware
priority: normal
severity: normal
status: open
title: Should AppVeyor run compile Python in debug mode?
versions: Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36215>
_______________________________________