This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients pablogsal, vstinner, zach.ware
Date 2019-03-06.17:16:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1551892607.07.0.699747283695.issue36215@roundup.psfhosted.org>
In-reply-to
Content
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...
History
Date User Action Args
2019-03-06 17:16:47vstinnersetrecipients: + vstinner, zach.ware, pablogsal
2019-03-06 17:16:47vstinnersetmessageid: <1551892607.07.0.699747283695.issue36215@roundup.psfhosted.org>
2019-03-06 17:16:47vstinnerlinkissue36215 messages
2019-03-06 17:16:46vstinnercreate