From: elns <el...@xs...> - 2024-10-23 08:48:19
|
On 10/22/24 21:02, François Vogel wrote: > > These tests are constrained by 'failsOnUbuntu'. Which is a bad name. I'm striving to improve this in > the less_tests_constraints branch but it's a long-term effort. > Ah, I'm concluding that I managed to make you misunderstand what I meant with my follow-up question. And I see why. Sorry. My follow-up question was targeted at the Tk tests when they are actually executing on Linux or on any Unix-derivative except macOS, and which do need an active window manager. (I already understood from your first reply that those tests must be somehow constrained so they don't run on CI). I realize now that my follow-up question presumes that Tk maintainers use some reference environment or preferred graphical environment. From your response, I realize only now that this presumption may be simply false. So, only if there is a reference graphical environment of sorts: - which window manager is being used? - does the wm run decoupled from / without a physical screen, like with xvfb? - does the wm run stand-alone, or does it run with a desktop environment being active? - if a desktop environment is active, then which one? - has all of this been documented/standardized as well? Sorry for the confusion, best regards, Erik. -- |