The failure in tearDownClass is a side-effect of the failure in test_set_keys causing 'p.set_keys_type = Func' being skipped.  That could be prevented with 'try:<anything that could fail>finally: p.set_keys_type = Func'.

I am completely puzzled at the sudden failure on one machine.  configdialog and test_configdialog were lasted changed 11 days ago (10/27) by Serhey's patch to make font samples editable.  test_idle passed consistently everywhere, including that machine, until build 121, 16 hours ago, and then suddenly started failing, consistently, on that one machine (as far as I know).  It continues to pass on my Win 10 machine, freshly updated with Python rebuilt.  I also checked the git log for tkinter.__init__ and tkinter.ttk and they have not been changed either.

The failure message is also a surprise.  'custom_keyset_on' is a ttk Radiobutton.
https://docs.python.org/3/library/tkinter.ttk.html#widget-states
does not list 'hover' as a state.  However
https://www.tcl.tk/man/tcl8.6/TkCmd/ttk_widget.htm#M-state
does (so the doc needs fixing): "The mouse cursor is within the widget."

Perhaps 'hover' is a result of previous mouse cursor positioning from event_generates in the font tab test.  (Why the sudden change on one system would still be a puzzle.)  If this is the reason, then I only need to worry about this one state test.

Otherwise, I would have to think about either parking the cursor where it cannot interfere, or about minimizing the dialog when it does not need to be de-iconified for event_generate to work.

Serhiy, any thoughts on this?