New Windows 11 build worker
![](https://secure.gravatar.com/avatar/8da8dda10fd391c6f5d50703c40699fb.jpg?s=120&d=mm&r=g)
With Windows 11 due to be released on Tuesday, Oct 5, I have created a PR against the buildmaster-config repository adding a build worker just for this.
It's brand new dedicated hardware capable of running 40 parallel tests taking ~ 2 min 30 sec.
Test time is now limited by process creation time:
0:02:33 load avg: 2.14 [427/427/1] test_multiprocessing_spawn passed (2 min 17 sec)
Total duration: 2 min 33 sec
Note that the failed test is test_winconsoleio. I'm assuming something changed in this release of Windows meaning getting this worker going will help track that down :)
Once the PR is merged, the worker is ready to go, I just need to start the service (the build master will use my existing password).
-- Jeremy Kloth
![](https://secure.gravatar.com/avatar/8da8dda10fd391c6f5d50703c40699fb.jpg?s=120&d=mm&r=g)
Note that the failed test is test_winconsoleio. I'm assuming something changed in this release of Windows meaning getting this worker going will help track that down :)
I've created an issue for tracking the test_winconsoleio error:
https://bugs.python.org/issue45354
-- Jeremy Kloth
![](https://secure.gravatar.com/avatar/8da8dda10fd391c6f5d50703c40699fb.jpg?s=120&d=mm&r=g)
On Sun, Oct 3, 2021 at 8:46 AM Jeremy Kloth <jeremy.kloth@gmail.com> wrote:
I've created an issue for tracking the test_winconsoleio error:
PR submitted to fix the apparently more strict handling of device naming.
-- Jeremy Kloth
participants (1)
-
Jeremy Kloth