[Twisted-Python] close to the finish line on hosted windows testing
![](https://secure.gravatar.com/avatar/e1554622707bedd9202884900430b838.jpg?s=120&d=mm&r=g)
Thanks to Craig and Adi's work, we now have tests sort of working on appveyor. However, they aren't actually reporting their pass/fail status right now as github statuses, I am assuming because of the persistent failures that were causing noise on unrelated tickets. However, it's very close to being a useful builder; there are really only 2 remaining issues, not counting turning on the reporting itself. I've made an umbrella ticket here: https://twistedmatrix.com/trac/ticket/8664 <https://twistedmatrix.com/trac/ticket/8664> and documented what's wrong with each one. So, if you care about Twisted on Windows, fixing the issues documented there should make it much easier for more folks to contribute easily :). -glyph
![](https://secure.gravatar.com/avatar/c194a4d2f2f8269aa052942e87985198.jpg?s=120&d=mm&r=g)
On 24 July 2016 at 20:07, Amber "Hawkie" Brown <hawkowl@atleastfornow.net> wrote:
Just an update on this. We got a $130/month credit sponsored by MS for Azure VMs, including Windows 8.1 and Windows 10 VMs. Right now I don't have time to manage a Windows buildslave, but if someone want to maintain the buildbot slaves on Windows I can take care of creating the VM and give the required access and I can also take care of updating the buildbot configuration. The Appveyor build is pretty responsive and is available to anyone... so hosted Windows is not a top priority. I think that Appveyor only runs on a single Windows Server flavor... so with Azure we can also have desktop flavors. For security reasons Buildbot slaves are accessible only to the Twisted team members, and this reduces their usefulness. The goal is to have latent slaves starting from a snapshot and running all PRs even if they are from forks. If you are already running latest buildbot slaves on Azure and want to share your infrastructure code, please let me know as it would be of great help. I have never used Azure API and I am just starting to learn how it works. --------- Even if we don't run Azure VMs, the Azure account is of great help as it makes it easier to publish the Windows wheels generated on Appveyor using the Azure Blob storage Many thanks to Microsoft for providing access to these VMs and for the MSDN subscription.T -- Adi Roiban
![](https://secure.gravatar.com/avatar/c194a4d2f2f8269aa052942e87985198.jpg?s=120&d=mm&r=g)
On 24 July 2016 at 20:07, Amber "Hawkie" Brown <hawkowl@atleastfornow.net> wrote:
Just an update on this. We got a $130/month credit sponsored by MS for Azure VMs, including Windows 8.1 and Windows 10 VMs. Right now I don't have time to manage a Windows buildslave, but if someone want to maintain the buildbot slaves on Windows I can take care of creating the VM and give the required access and I can also take care of updating the buildbot configuration. The Appveyor build is pretty responsive and is available to anyone... so hosted Windows is not a top priority. I think that Appveyor only runs on a single Windows Server flavor... so with Azure we can also have desktop flavors. For security reasons Buildbot slaves are accessible only to the Twisted team members, and this reduces their usefulness. The goal is to have latent slaves starting from a snapshot and running all PRs even if they are from forks. If you are already running latest buildbot slaves on Azure and want to share your infrastructure code, please let me know as it would be of great help. I have never used Azure API and I am just starting to learn how it works. --------- Even if we don't run Azure VMs, the Azure account is of great help as it makes it easier to publish the Windows wheels generated on Appveyor using the Azure Blob storage Many thanks to Microsoft for providing access to these VMs and for the MSDN subscription.T -- Adi Roiban
participants (3)
-
Adi Roiban
-
Amber "Hawkie" Brown
-
Glyph Lefkowitz