| Age | Commit message (Collapse) | Author |
|---|
|
Problem: Testing with Python on AppVeyor does not work properly.
Solution: Fix typo. Move most lines to the .bat file. (Christopher
Plewright, closes #11828)
|
|
Problem: AppVeyor builds with an old Python version.
Solution: Switch from Python 3.8 to 3.11. (Christopher Plewright,
closes #11814)
|
|
Problem: AppVeyor runs much slower with MSVC 2022.
Solution: Go back to MSVC 2015. (Christopher Plewright, closes #11810)
|
|
Problem: AppVeyor uses some older tools.
Solution: Switch to Visual Studio 2022 and Python 3.11. (Christopher
Plewright, closes #11793)
|
|
Problem: MS-Windows: clumsy way to suppress progress on CI.
Solution: Check for "$CI" in the Makefile itself. (Ken Takata, closes #9631)
|
|
Problem: Appveyor script does not detect nmake failure.
Solution: Explicitly check for executable. (Ken Takata, closes #8281)
|
|
Problem: MS-Windows tests on AppVeyor are slow.
Solution: Use GitHub Actions. (Ken Takata, closes #6569)
|
|
Problem: Appveyor output doesn't show MinGW console features.
Solution: List the features of the console build.
|
|
Problem: Appveyor build with MSVC fails puts progress bar in log.
Solution: Adjust the sed command. (Ken Takata)
|
|
Problem: Appveyor build with MSVC fails.
Solution: Remove the sed command
|
|
Problem: Travis CI script is too complicated.
Solution: Add names to environments. Move appveyor script outside of src
directory. (Ozaki Kiichi, closes #3890)
|
