[tahoe-lafs-trac-stream] [Tahoe-LAFS] #3477: Omit installing vcpython27 on Windows CI

[Tahoe-LAFS]

#3477: Omit installing vcpython27 on Windows CI
------------------------------------+---------------------------
     Reporter:  sajith              |      Owner:  sajith
         Type:  task                |     Status:  new
     Priority:  normal              |  Milestone:  undecided
    Component:  dev-infrastructure  |    Version:  n/a
   Resolution:                      |   Keywords:  review-needed
Launchpad Bug:                      |
------------------------------------+---------------------------

Comment (by sajith):

 I published zfec 1.5.4 on 2020 October 15, but it turned out that wheel
 package for Windows + Python 2.7 was broken. Tahoe-LAFS CI failed to use
 zfec-1.5.4, with this error message:

 {{{
 zfec: None [(<type 'exceptions.ImportError'>, 'DLL load failed: %1 is not
 a valid Win32 application.', ('d:\\a\\tahoe-lafs\\tahoe-
 lafs\\.tox\\py27-coverage\\lib\\site-packages\\zfec\\__init__.py', 13,
 '<module>', 'from ._fec import Encoder, Decoder, Error'))]
 }}}

 (Seems that those error messages when CI was restarted.)

 [[https://github.com/tahoe-lafs/zfec/issues/34|This]] is the corresponding
 issue on zfec's tracker.  I went ahead and deleted zfec 1.5.4 wheel files
 packaged for Windows from PyPI, in order to avoid further CI disruption.

 I've uploaded zfec 1.5.5 to pypi today (2020 November 12), which has been
 tested a little more. I updated cibuildwheel version that builds zfec
 packages, added a step to check that the package cibuildwheel just built
 is actually usable, and did some manual testing on Windows and macOS.
 Finally, re-running Tahoe's test suite on !GitHub Actions has
 [[https://github.com/tahoe-lafs/tahoe-
 lafs/pull/862/checks?check_run_id=1390804176|confirmed]] that this time
 zfec is usable.

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3477#comment:3>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage