3681 Use x86 Python for Windows testing #1047
No reviewers
Labels
No Label
Benchmarking and Performance
HTTP Storage Protocol
Nevow Removal
Python 3 Porting
not-for-merge
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: tahoe-lafs/tahoe-lafs#1047
Loading…
Reference in New Issue
No description provided.
Delete Branch "3681.github-actions-use-x86-windows"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Ticket is https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3681.
Microsoft seems to have removed Microsoft Visual C++ Compiler for Python 2.7 downloads from their website, and it has broken our CI. Among Tahoe-LAFS dependencies, the only Python package that needs vcpython27 is netutils, and netutils ships a
cp27-cp27m-win32
wheel package, and nocp27-cp27m-win_amd64
. This change will switch to 32-bit Python for Windows testing.Ideally we should be only switching to 32-bit Python 2.7 and leave Python 3.6 setup alone, but I could not figure out the GitHub Actions magic incantation to do that. Commits in this PR and their corresponding CI failures will bear witness to that. ;-)
Coverage remained the same at 95.113% when pulling
6d1b95b965
on 3681.github-actions-use-x86-windows into6142168977
on master.I am not sure 32-bit vs 64-bit makes much difference for Tahoe-LAFS, but ... you can apply the suggestion I made, or not.
You can do
{{ matrix.os == 'windows-latest' && matrix.python-version == '3.6' }}
I believe.Sadly GitHub Actions skipped right over this:
... and chose to use the next step instead:
See https://github.com/tahoe-lafs/tahoe-lafs/pull/1047/checks?check_run_id=2442603808
Seems that this works: