Tk Source Code

Timeline
Login

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

5 check-ins related to "ci-test-exit-status"

2026-11-17
17:15
Fix [ead4782b08]: the test suite exited with status 0 when tests failed, so CI reported success, even when no test ran check-in: d18552b3 user: jan.nijtmans tags: trunk, main
15:13
Rebase to trunk closed check-in: 1f9358e2 user: jan.nijtmans tags: ci-test-exit-status
14:56
Fix for [f64df5e666]: Remove unused troughGC and copyGC from MacScrollbar (thanks to Christopher Chavez) check-in: fd36ad56 user: csaba tags: trunk, main
2026-11-16
09:58
Fix [ead4782b08]: the test suite exited with status 0 when tests failed, so CI reported success, even when no test ran. Under Tk, tcltest exits with status 0 at the end of runAllTests, before it reports test files with errors and returns its result (Tcl ticket 7abc1460c0). all.tcl now prevents that exit and exits with the result of runAllTests when ERROR_ON_FAILURES is set; tests/all.tcl skips the ttk directory explicitly, since runAllTests now reaches it. The Linux and macOS workflows run both the classic and the ttk tests and fail if either exited with an error. On Windows, where the exit status is lost in the pipe through cat32, the workflow requires a summary with at least one test, no failures and no test file errors. (user: serhiy.storchaka) check-in: 6f50976f user: serhiy.storchaka tags: ci-test-exit-status
09:22
tests/font.test: use TkFixedFont on win32 instead of "courier 12". See ticket [deca13e833]. Thanks to Serhiy Storchaka. check-in: 2e318316 user: erikleunissen tags: trunk, main