summaryrefslogtreecommitdiffstats
path: root/.github/workflows
Commit message (Collapse)AuthorAgeFilesLines
* upload-artifact@v3jan.nijtmans2022-12-021-2/+2
|
* Let the Github Actions CI runner build in both release and debug modes with ↵fvogel2022-10-161-21/+26
| | | | MSVC. Also, upgrade from windows-2019 to windows-2022 when building with MSVC, so that issue [d93c8175fd] triggers.
* Run Tk testcases on ubuntu-20.04 for now (some are failing on ubuntu-22.04)jan.nijtmans2022-08-231-1/+1
|\
| * Run GITHUB actions testcases with tcl 8.5 -> 8.6 (since ubuntu 20.04 doesn't ↵jan.nijtmans2022-08-231-4/+4
| | | | | | | | have tcl8.5-dev package any more)
* | Github action: ubuntu-20.04 -> ubuntu-22.04jan.nijtmans2022-08-221-2/+2
|\ \ | |/
| * ubuntu-18.04 is deprecatedjan.nijtmans2022-08-221-2/+2
| |
* | actions/checkout@v2 -> actions/checkout@v3jan.nijtmans2022-05-273-11/+11
|\ \ | |/
| * actions/checkout@v2 -> actions/checkout@v3jan.nijtmans2022-05-273-6/+6
| |
* | Merge 8.5jan.nijtmans2022-05-223-0/+6
|\ \ | |/
| * See: [https://github.com/tcltk/tcl/pull/13]jan.nijtmans2022-05-223-0/+6
| |
* | Merge 8.5jan.nijtmans2022-01-171-1/+1
|\ \ | |/
| * Add '--disable-xft' on MacOSX Github ACTIONS builds. Thanks, François, for ↵jan.nijtmans2022-01-171-1/+1
| | | | | | | | the suggestion!
| * Don't bother a "make install" on MacOS either.jan.nijtmans2021-07-281-7/+0
| |
* | Merge 8.5jan.nijtmans2021-07-201-1/+4
|\ \ | |/
| * (redo) start to use msys2 shell: If the right tools are installed, it worksjan.nijtmans2021-07-201-1/+4
| |
* | Merge 8.5jan.nijtmans2021-07-171-1/+1
|\ \ | |/
| * Undo part of previous commit: msys2 shell behaves different from bashjan.nijtmans2021-07-171-1/+1
| |
* | Merge 8.5jan.nijtmans2021-07-161-4/+3
|\ \ | |/
| * Use msys2 shell in msys environmentjan.nijtmans2021-07-161-4/+3
| |
* | Merge 8.5jan.nijtmans2021-07-161-2/+2
|\ \ | |/
| * Install Msys2 the same way as Tcl doesjan.nijtmans2021-07-161-2/+2
| |
| * Test Tk 8.5 on MacOS with XQuarz onlyjan.nijtmans2021-05-261-20/+10
| |
| * Cherrypick [9d22c7e3] and adapt it to core-8-5-branch.fvogel2021-05-251-8/+16
| |
* | Add running of the test suite (deployment and development targets) for the ↵fvogel2021-05-241-0/+9
| | | | | | | | xcode job
* | Revert the logic of grepping in the output file because we need an exit code ↵fvogel2021-05-241-4/+13
| | | | | | | | of 0 for grep. As a consequence we need to grep separately in each (classic and ttk) output file. Finally restore proper killing of xvfb.
* | Only install X11 (Xquartz) when required. Fix the test checking this.fvogel2021-05-241-5/+4
| |
* | Dittofvogel2021-05-241-1/+1
| |
* | According to GitHub Actions documentation ( ↵fvogel2021-05-241-1/+1
| | | | | | | | https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on ), the correct runner for macOs Big Sur is macos-11, not macos-11.0. Follow the doc, even if it was working with macos-11.0
* | Merge 8.5jan.nijtmans2021-05-221-3/+2
|\ \ | |/
| * Merge mac_workflow branchjan.nijtmans2021-05-221-3/+2
| |\
| | * merge core-8-6-branchfvogel2021-05-211-2/+2
| | |\ | |_|/ |/| |
* | | unofficial -> snapshotjan.nijtmans2021-04-291-2/+2
| | |
| | * Previous commit shows a segfault in wm.test. Narrow down at which test this ↵fvogel2021-05-121-1/+1
| | | | | | | | | | | | happens.
| | * Theory: kill $XVFB_PID returns 1 because xvfb is no longer alive. Actually ↵fvogel2021-05-111-1/+0
| | | | | | | | | | | | we should not need to kill xvfb when process exits: line ( runXvfb :0; make test-classic test-ttk; exit $? ) should be enough.
| | * Force kill exit code to be zero, and make error message more specific.fvogel2021-05-111-2/+2
| | |
| | * Oops.fvogel2021-05-101-1/+1
| | |
| | * Hmmm... the exit code should probably rather be forced after the xvfb ↵fvogel2021-05-101-2/+2
| | | | | | | | | | | | killing. But let's first propagate the exit code from make test to the end of xvfb kill (see man kill: 'The value of $? after the trap action completes shall be the value it had before trap was invoked.')
| | * Try forcing exit code to be zero (grepping for 'Failed [1-9] could be good ↵fvogel2021-05-101-1/+1
| | | | | | | | | | | | enough).
| | * Not sure we need to explicitely exit $? . Try without.fvogel2021-05-091-1/+1
| | |
| | * Apply recommendation from the XQuartz (xvfb) guys ↵fvogel2021-05-081-1/+1
| | | | | | | | | | | | [https://github.com/XQuartz/XQuartz/issues/162#issuecomment-833215208]
| | * Previous commit results in 'Error: Cask 'xquartz@2.7' is unavailable: No ↵fvogel2021-05-031-3/+2
| | | | | | | | | | | | Cask with this name exists.'. Forget about this way, then.
| | * ... and in the process remove previous failing tries.fvogel2021-05-021-3/+1
| | |
| | * Try searching what versions are available, and install version 2.7 of XQuartz...fvogel2021-05-021-1/+2
| | |
| | * Add debug output.fvogel2021-04-281-2/+2
| | |
| | * Another tryfvogel2021-04-271-1/+3
| | |
| | * Last commit was a progress, the error message is no longer the same. Now try ↵fvogel2021-04-261-1/+1
| | | | | | | | | | | | a different display ID.
| | * Try -nolisten unix when launching xvfb in the hope the tests will run on ↵fvogel2021-04-251-1/+1
| |/ |/| | | | | macOS with clang.
* | Merge 8.5jan.nijtmans2021-03-151-2/+0
|\ \ | |/
* | Mark more testcases with failsOnXQuarzjan.nijtmans2021-03-081-6/+2
|\ \ | |/
* | Merge 8.5jan.nijtmans2021-01-211-4/+3
|\ \
generated by cgit v0.12 at 2026-02-12 16:22:17 (GMT)