- cmucl-cvs - mailman3.common-lisp.net

[Git][cmucl/cmucl][issue-464-lisp-version-uses-branch-name] Do something different for the master branch
by Raymond Toy (＠rtoy) 08 Feb '26

08 Feb '26

Raymond Toy pushed to branch issue-464-lisp-version-uses-branch-name at cmucl / cmucl Commits: 9467db45 by Raymond Toy at 2026-02-08T12:02:18-08:00 Do something different for the master branch On the master branch, use the version from "git describe --dirty". This way, the version for builds on the master branch can be distinguished by the number of commits since the last release/tag. Otherwise, we'll use the most recent tag or branch name, as before. - - - - - 1 changed file: - bin/git-version.sh Changes: ===================================== bin/git-version.sh ===================================== @@ -36,37 +36,39 @@ if [ -n "$VERSION" ]; then GIT_HASH="$VERSION" DEFAULT_VERSION="$VERSION" else - # The option --all allows use to use the the branch name or tag - # name as appropriate. This is much more informative. However, - # we have to remove everything before the first slash which - # contains things like "tag/" or "head/". - GIT_DESC="`git describe --all --dirty || git describe 2>/dev/null`" - GIT_HASH="`echo ${GIT_DESC} | sed 's;^[^/]*/;;' 2>/dev/null`" - BRANCH="`git rev-parse --abbrev-ref HEAD`*" + # Get the current branch. + BRANCH="`git rev-parse --abbrev-ref HEAD`" + if [ "$BRANCH" = "master" ]; then + # On the master branch, use simple git describe --dirty for the version + DEFAULT_VERSION="`git describe --all || git describe 2>/dev/null`" + else + # We're not on the master branch. Do something different. + # The option --all allows use to use the the branch name or tag + # name as appropriate. This is much more informative. However, + # we have to remove everything before the first slash which + # contains things like "tag/" or "head/". + GIT_DESC="`git describe --all --dirty || git describe 2>/dev/null`" + GIT_HASH="`echo ${GIT_DESC} | sed 's;^[^/]*/;;' 2>/dev/null`" - case "$GIT_HASH" in - snapshot-[0-9][0-9][0-9][0-9]-[01][0-9]) - # The git hash looks like snapshot-yyyy-mm-<stuff>. Remove the - # "snapshot-" part. - DEFAULT_VERSION=`expr "$GIT_HASH" : "snapshot-$.*$"` - ;; - [0-9][0-9][a-f]) - # The git hash looks like a release which is 3 hex digits. - # Use it as is. - DEFAULT_VERSION="${GIT_HASH}" - ;; - ${BRANCH}*) - # The hash looks like the current branch with possibly more - # stuff at the end. Use the hash as the version. - DEFAULT_VERSION="${GIT_HASH}" - ;; - [0-9]*) - # Assuming this is CI which seems to produce a githash like - # "pipeline/<digits>". Make the version include "ci-" so we - # know this was done via CI. - DEFAULT_VERSION="ci-${GIT_HASH}" - ;; - esac + case "$GIT_HASH" in + snapshot-[0-9][0-9][0-9][0-9]-[01][0-9]) + # The git hash looks like snapshot-yyyy-mm-<stuff>. Remove the + # "snapshot-" part. + DEFAULT_VERSION=`expr "$GIT_HASH" : "snapshot-$.*$"` + ;; + [0-9][0-9][a-f]) + # The git hash looks like a release which is 3 hex digits. + # Use it as is. + DEFAULT_VERSION="${GIT_HASH}" + ;; + [0-9]*) + # Assuming this is CI which seems to produce a githash like + # "pipeline/<digits>". Make the version include "ci-" so we + # know this was done via CI. + DEFAULT_VERSION="ci-${GIT_HASH}" + ;; + esac + fi if [ -z "$DEFAULT_VERSION" ]; then echo "Unable to determine a default version from git describe: $GIT_DESC" View it on GitLab: https://gitlab.common-lisp.net/cmucl/cmucl/-/commit/9467db45738f62bf9e06d4c… -- View it on GitLab: https://gitlab.common-lisp.net/cmucl/cmucl/-/commit/9467db45738f62bf9e06d4c… You're receiving this email because of your account on gitlab.common-lisp.net.

1 0

[Git][cmucl/cmucl][issue-471-test-cases-for-pow] Adjust pow.case.9 for core-math
by Raymond Toy (＠rtoy) 07 Feb '26

07 Feb '26

Raymond Toy pushed to branch issue-471-test-cases-for-pow at cmucl / cmucl Commits: 6011e629 by Raymond Toy at 2026-02-06T17:25:39-08:00 Adjust pow.case.9 for core-math Looks like cr_pow does what std::pow says for 1^exp for any exp and (-1)^(+/-inf) is 1. No errors signaled. Update the test for core-math. - - - - - 1 changed file: - tests/fdlibm.lisp Changes: ===================================== tests/fdlibm.lisp ===================================== @@ -785,10 +785,27 @@ (define-test %pow.case.9 (:tag :fdlibm) + ;; std::pow says 1^exp is 1 for any exp, including NaN. (-1)^(+/-inf) + ;; is 1. No errors signaled. + #+core-math + (progn + (assert-equal 1d0 + (kernel:%pow 1d0 ext:double-float-positive-infinity)) + (assert-equal 1d0 + (kernel:%pow 1d0 ext:double-float-negative-infinity)) + (assert-equal 1d0 + (kernel:%pow 1d0 *qnan*)) + (assert-equal 1d0 + (kernel:%pow -1d0 ext:double-float-positive-infinity)) + (assert-equal 1d0 + (kernel:%pow -1d0 ext:double-float-negative-infinity))) + #-core-math ;; +-1 ^ +-inf is NaN. ;; ;; But the implementation signals invalid operation, so we need to ;; check for that. + ;; + (progn (assert-error 'floating-point-invalid-operation (kernel:%pow 1d0 ext:double-float-positive-infinity)) (assert-error 'floating-point-invalid-operation @@ -805,7 +822,7 @@ (assert-true (ext:float-nan-p (kernel:%pow -1d0 ext:double-float-positive-infinity))) (assert-true (ext:float-nan-p - (kernel:%pow -1d0 ext:double-float-negative-infinity))))) + (kernel:%pow -1d0 ext:double-float-negative-infinity)))))) (define-test %pow.case.10 (:tag :fdlibm) View it on GitLab: https://gitlab.common-lisp.net/cmucl/cmucl/-/commit/6011e6296a16d7d7ca253ce… -- View it on GitLab: https://gitlab.common-lisp.net/cmucl/cmucl/-/commit/6011e6296a16d7d7ca253ce… You're receiving this email because of your account on gitlab.common-lisp.net.

1 0

[Git][cmucl/cmucl] Pushed new branch issue-471-test-cases-for-pow
by Raymond Toy (＠rtoy) 06 Feb '26

06 Feb '26

Raymond Toy pushed new branch issue-471-test-cases-for-pow at cmucl / cmucl -- View it on GitLab: https://gitlab.common-lisp.net/cmucl/cmucl/-/tree/issue-471-test-cases-for-… You're receiving this email because of your account on gitlab.common-lisp.net.

1 0

[Git][cmucl/cmucl][issue-468-core-math-signals] 7 commits: Define macros to handle invalid and overflow signals
by Raymond Toy (＠rtoy) 06 Feb '26

06 Feb '26

Raymond Toy pushed to branch issue-468-core-math-signals at cmucl / cmucl Commits: 3fa81f34 by Raymond Toy at 2026-02-03T08:32:45-08:00 Define macros to handle invalid and overflow signals - - - - - 9a4f3d7e by Raymond Toy at 2026-02-04T08:06:20-08:00 Minor cleanup of GNUMakefile First, CORE64_OBJS is no longer defined, so don't use it. The CORE64_OBJS that used to name the .o files for core-math are now computed as part of OBJS. This removal also meant that the "clean" target no longer removed the core-math object files. Fix this by changing the rule to remove $(OBJS) instead of *.o. - - - - - f5a798b8 by Raymond Toy at 2026-02-05T17:51:48-08:00 Fix #470: Fix unit test issues on Ubuntu CI - - - - - 5b6d4d73 by Raymond Toy at 2026-02-05T17:51:48-08:00 Merge branch 'issue-470-ubuntu-ci-failures' into 'master' Fix #470: Fix unit test issues on Ubuntu CI Closes #470 See merge request cmucl/cmucl!348 - - - - - 772641b9 by Raymond Toy at 2026-02-05T19:39:14-08:00 Fix #469: Reenable cr_pow - - - - - 6ac1b6b4 by Raymond Toy at 2026-02-05T19:39:14-08:00 Merge branch 'issue-469-enable-cr-pow' into 'master' Fix #469: Reenable cr_pow Closes #469 and #470 See merge request cmucl/cmucl!346 - - - - - f795ec67 by Raymond Toy at 2026-02-05T20:28:36-08:00 Merge branch 'master' into issue-468-core-math-signals - - - - - 6 changed files: - .gitlab-ci.yml - bin/run-unit-tests.sh - src/lisp/GNUmakefile - src/lisp/irrat.c - tests/issues.lisp - + tests/test-run-prog/ls-link Changes: ===================================== .gitlab-ci.yml ===================================== @@ -147,7 +147,9 @@ linux:build: - job: linux:install artifacts: true variables: - CONFIG: "x86_linux_clang" + # Fedora 41 must build with gcc because the clang build fails some + # ansi-tests. See [#469]. + CONFIG: "x86_linux" # These rules is needed so that the static analyzer job can run on a # schedule because this is a prerequisite of the analyzer build. A # regular push or merge request does the normal stuff. @@ -171,7 +173,7 @@ linux:cross-build: - linux-4/lisp variables: # This must match the config used for the linux build! - CONFIG: "x86_linux_clang" + CONFIG: "x86_linux" needs: @@ -346,7 +348,10 @@ ubuntu:build: - job: ubuntu:install artifacts: true variables: - CONFIG: "x86_linux_clang" + # Build with gcc on Ubuntu 25.10. It produces a lisp than passes + # the ansi-tests. Clang seems to fail the ansi-tests WRITE.1, + # PRINT.1, and friends when cr_pow is used. + CONFIG: "x86_linux" ubuntu:test: <<: *unit_test_configuration ===================================== bin/run-unit-tests.sh ===================================== @@ -42,9 +42,9 @@ done shift $((OPTIND - 1)) # Create the test directory needed by the issue.45 test. -rm -rf test-tmp -mkdir test-tmp -ln -s /bin/ls test-tmp/ls-link +#rm -rf test-tmp +#mkdir test-tmp +#ln -s /bin/ls test-tmp/ls-link # Set the timestamps on 64-bit-timestamp-2038.txt and # 64-bit-timestamp-2106.txt, but only for OSes where we know this @@ -56,8 +56,9 @@ ln -s /bin/ls test-tmp/ls-link # tests/os.lisp. case `uname -s` in Linux) - touch -d "1 April 2038" tests/resources/64-bit-timestamp-2038.txt - touch -d "1 April 2106" tests/resources/64-bit-timestamp-2106.txt + # -t format is [[CC]YY]MMDDhhmm[.ss] + touch -t 203804010000 tests/resources/64-bit-timestamp-2038.txt + touch -t 210604010000 tests/resources/64-bit-timestamp-2106.txt ;; esac ===================================== src/lisp/GNUmakefile ===================================== @@ -55,7 +55,7 @@ version.o : version.c version mv ,version version $(CC) ${CFLAGS} $(CPPFLAGS) -DVERSION=`cat version` -c $< -lisp: ${OBJS} ${CORE64_OBJS} version.o +lisp: ${OBJS} version.o $(CC) -g ${OS_LINK_FLAGS} -o ,lisp $^ ${OS_LIBS} -lm mv -f ,lisp lisp @@ -75,7 +75,7 @@ internals.h internals.inc: @false clean: - $(RM) Depends *.o $(CORE64_OBJS) lisp lisp.nm core lisp.a + $(RM) Depends $(OBJS) lisp lisp.nm core lisp.a echo 'Map file for lisp version 0' > lisp.nm depend: Depends ===================================== src/lisp/irrat.c ===================================== @@ -39,14 +39,21 @@ extern void cr_sincos(double, double *, double *); * Wrappers for the special functions */ +#define MAYBE_SIGNAL_INVALID(test, val) \ + if ((test)) { \ + return fdlibm_setexception(val, FDLIBM_INVALID); \ + } + +#define MAYBE_SIGNAL_OVERFLOW(x) \ + if (isinf(x)) { \ + return fdlibm_setexception(x, FDLIBM_OVERFLOW); \ + } + double lisp_sin(double x) { #ifdef FEATURE_CORE_MATH - /* Signals invalid if x is infinite */ - if (isinf(x)) { - return fdlibm_setexception(x, FDLIBM_INVALID); - } + MAYBE_SIGNAL_INVALID(isinf(x), x) return cr_sin(x); #else @@ -58,10 +65,7 @@ double lisp_cos(double x) { #ifdef FEATURE_CORE_MATH - /* Signals invalid if x is infinite */ - if (isinf(x)) { - return fdlibm_setexception(x, FDLIBM_INVALID); - } + MAYBE_SIGNAL_INVALID(isinf(x), x) return cr_cos(x); #else @@ -73,10 +77,7 @@ double lisp_tan(double x) { #ifdef FEATURE_CORE_MATH - /* Signals invalid if x is infinite */ - if (isinf(x)) { - return fdlibm_setexception(x, FDLIBM_INVALID); - } + MAYBE_SIGNAL_INVALID(isinf(x), x) return cr_tan(x); #else @@ -128,10 +129,7 @@ double lisp_sinh(double x) { #ifdef FEATURE_CORE_MATH - /* Signal overflow if x is infinite */ - if (isinf(x)) { - return fdlibm_setexception(x, FDLIBM_OVERFLOW); - } + MAYBE_SIGNAL_OVERFLOW(x) return cr_sinh(x); #else @@ -163,10 +161,7 @@ double lisp_asinh(double x) { #ifdef FEATURE_CORE_MATH - /* Signal overflow if x is infinite */ - if (isinf(x)) { - return fdlibm_setexception(x, FDLIBM_OVERFLOW); - } + MAYBE_SIGNAL_OVERFLOW(x) return cr_asinh(x); #else @@ -178,14 +173,9 @@ double lisp_acosh(double x) { #ifdef FEATURE_CORE_MATH - /* Signals invalid if x is not in the domain x >= 1 */ - if (x < 1) { - return fdlibm_setexception(x, FDLIBM_INVALID); - } - /* Signal overflow if x is infinite */ - if (isinf(x)) { - return fdlibm_setexception(x, FDLIBM_OVERFLOW); - } + MAYBE_SIGNAL_INVALID(x < 1, x) + + MAYBE_SIGNAL_OVERFLOW(x) return cr_acosh(x); #else @@ -236,13 +226,17 @@ lisp_log10(double x) double lisp_pow(double x, double y) { +#ifdef FEATURE_CORE_MATH /* - * cr_pow seems causes ansi-tests to fail in test WRITE.1 among - * others. Somewhere an invalid operation is occurring. Thus - * just use fdlibm for now until we can figure out what's causing - * the failure. + * cr_pow when compiled with older versions of gcc or clang can + * cause failures in the ansi-tests [#469]. Ubuntu 25.10 and Fedora 41 + * (gcc only) are known to have compilers that work well enough + * that the ansi-tests pass. */ + return cr_pow(x, y); +#else return __ieee754_pow(x, y); +#endif } double ===================================== tests/issues.lisp ===================================== @@ -436,7 +436,7 @@ (define-test issue.45 (:tag :issues) ;; This depends on run-tests to setup the test directory correctly! - (let* ((test-dir #p"test-tmp/") + (let* ((test-dir #p"tests/test-run-prog/") (test-dir-name (namestring test-dir))) (flet ((do-test (program) (with-output-to-string (s) ===================================== tests/test-run-prog/ls-link ===================================== @@ -0,0 +1,2 @@ +#! /bin/sh +exec /bin/ls "$@" View it on GitLab: https://gitlab.common-lisp.net/cmucl/cmucl/-/compare/730da685588abfcad4b932… -- View it on GitLab: https://gitlab.common-lisp.net/cmucl/cmucl/-/compare/730da685588abfcad4b932… You're receiving this email because of your account on gitlab.common-lisp.net.

1 0

[Git][cmucl/cmucl][master] 2 commits: Fix #469: Reenable cr_pow
by Raymond Toy (＠rtoy) 06 Feb '26

06 Feb '26

Raymond Toy pushed to branch master at cmucl / cmucl Commits: 772641b9 by Raymond Toy at 2026-02-05T19:39:14-08:00 Fix #469: Reenable cr_pow - - - - - 6ac1b6b4 by Raymond Toy at 2026-02-05T19:39:14-08:00 Merge branch 'issue-469-enable-cr-pow' into 'master' Fix #469: Reenable cr_pow Closes #469 and #470 See merge request cmucl/cmucl!346 - - - - - 3 changed files: - .gitlab-ci.yml - bin/run-unit-tests.sh - src/lisp/irrat.c Changes: ===================================== .gitlab-ci.yml ===================================== @@ -147,7 +147,9 @@ linux:build: - job: linux:install artifacts: true variables: - CONFIG: "x86_linux_clang" + # Fedora 41 must build with gcc because the clang build fails some + # ansi-tests. See [#469]. + CONFIG: "x86_linux" # These rules is needed so that the static analyzer job can run on a # schedule because this is a prerequisite of the analyzer build. A # regular push or merge request does the normal stuff. @@ -171,7 +173,7 @@ linux:cross-build: - linux-4/lisp variables: # This must match the config used for the linux build! - CONFIG: "x86_linux_clang" + CONFIG: "x86_linux" needs: @@ -346,7 +348,10 @@ ubuntu:build: - job: ubuntu:install artifacts: true variables: - CONFIG: "x86_linux_clang" + # Build with gcc on Ubuntu 25.10. It produces a lisp than passes + # the ansi-tests. Clang seems to fail the ansi-tests WRITE.1, + # PRINT.1, and friends when cr_pow is used. + CONFIG: "x86_linux" ubuntu:test: <<: *unit_test_configuration ===================================== bin/run-unit-tests.sh ===================================== @@ -41,6 +41,11 @@ done # Shift out the options shift $((OPTIND - 1)) +# Create the test directory needed by the issue.45 test. +#rm -rf test-tmp +#mkdir test-tmp +#ln -s /bin/ls test-tmp/ls-link + # Set the timestamps on 64-bit-timestamp-2038.txt and # 64-bit-timestamp-2106.txt, but only for OSes where we know this # works. (This is so we don't an annoying error message from touch ===================================== src/lisp/irrat.c ===================================== @@ -202,13 +202,17 @@ lisp_log10(double x) double lisp_pow(double x, double y) { +#ifdef FEATURE_CORE_MATH /* - * cr_pow seems causes ansi-tests to fail in test WRITE.1 among - * others. Somewhere an invalid operation is occurring. Thus - * just use fdlibm for now until we can figure out what's causing - * the failure. + * cr_pow when compiled with older versions of gcc or clang can + * cause failures in the ansi-tests [#469]. Ubuntu 25.10 and Fedora 41 + * (gcc only) are known to have compilers that work well enough + * that the ansi-tests pass. */ + return cr_pow(x, y); +#else return __ieee754_pow(x, y); +#endif } double View it on GitLab: https://gitlab.common-lisp.net/cmucl/cmucl/-/compare/5b6d4d73d0748022cb160c… -- View it on GitLab: https://gitlab.common-lisp.net/cmucl/cmucl/-/compare/5b6d4d73d0748022cb160c… You're receiving this email because of your account on gitlab.common-lisp.net.

1 0

[Git][cmucl/cmucl][issue-469-enable-cr-pow] 4 commits: Minor cleanup of GNUMakefile
by Raymond Toy (＠rtoy) 06 Feb '26

06 Feb '26

Raymond Toy pushed to branch issue-469-enable-cr-pow at cmucl / cmucl Commits: 9a4f3d7e by Raymond Toy at 2026-02-04T08:06:20-08:00 Minor cleanup of GNUMakefile First, CORE64_OBJS is no longer defined, so don't use it. The CORE64_OBJS that used to name the .o files for core-math are now computed as part of OBJS. This removal also meant that the "clean" target no longer removed the core-math object files. Fix this by changing the rule to remove $(OBJS) instead of *.o. - - - - - f5a798b8 by Raymond Toy at 2026-02-05T17:51:48-08:00 Fix #470: Fix unit test issues on Ubuntu CI - - - - - 5b6d4d73 by Raymond Toy at 2026-02-05T17:51:48-08:00 Merge branch 'issue-470-ubuntu-ci-failures' into 'master' Fix #470: Fix unit test issues on Ubuntu CI Closes #470 See merge request cmucl/cmucl!348 - - - - - fb50ed76 by Raymond Toy at 2026-02-05T17:55:03-08:00 Merge branch 'master' into issue-469-enable-cr-pow - - - - - 0 changed files: Changes: View it on GitLab: https://gitlab.common-lisp.net/cmucl/cmucl/-/compare/ef6f16eca1f968af59a0e3… -- View it on GitLab: https://gitlab.common-lisp.net/cmucl/cmucl/-/compare/ef6f16eca1f968af59a0e3… You're receiving this email because of your account on gitlab.common-lisp.net.

1 0

[Git][cmucl/cmucl][issue-469-enable-cr-pow] Minor cleanup of GNUMakefile
by Raymond Toy (＠rtoy) 06 Feb '26

06 Feb '26

Raymond Toy pushed to branch issue-469-enable-cr-pow at cmucl / cmucl Commits: ef6f16ec by Raymond Toy at 2026-02-05T17:52:52-08:00 Minor cleanup of GNUMakefile First, CORE64_OBJS is no longer defined, so don't use it. The CORE64_OBJS that used to name the .o files for core-math are now computed as part of OBJS. This removal also meant that the "clean" target no longer removed the core-math object files. Fix this by changing the rule to remove $(OBJS) instead of *.o. - - - - - 1 changed file: - src/lisp/GNUmakefile Changes: ===================================== src/lisp/GNUmakefile ===================================== @@ -55,7 +55,7 @@ version.o : version.c version mv ,version version $(CC) ${CFLAGS} $(CPPFLAGS) -DVERSION=`cat version` -c $< -lisp: ${OBJS} ${CORE64_OBJS} version.o +lisp: ${OBJS} version.o $(CC) -g ${OS_LINK_FLAGS} -o ,lisp $^ ${OS_LIBS} -lm mv -f ,lisp lisp @@ -75,7 +75,7 @@ internals.h internals.inc: @false clean: - $(RM) Depends *.o $(CORE64_OBJS) lisp lisp.nm core lisp.a + $(RM) Depends $(OBJS) lisp lisp.nm core lisp.a echo 'Map file for lisp version 0' > lisp.nm depend: Depends View it on GitLab: https://gitlab.common-lisp.net/cmucl/cmucl/-/commit/ef6f16eca1f968af59a0e38… -- View it on GitLab: https://gitlab.common-lisp.net/cmucl/cmucl/-/commit/ef6f16eca1f968af59a0e38… You're receiving this email because of your account on gitlab.common-lisp.net.

1 0

[Git][cmucl/cmucl][master] 2 commits: Fix #470: Fix unit test issues on Ubuntu CI
by Raymond Toy (＠rtoy) 06 Feb '26

06 Feb '26

Raymond Toy pushed to branch master at cmucl / cmucl Commits: f5a798b8 by Raymond Toy at 2026-02-05T17:51:48-08:00 Fix #470: Fix unit test issues on Ubuntu CI - - - - - 5b6d4d73 by Raymond Toy at 2026-02-05T17:51:48-08:00 Merge branch 'issue-470-ubuntu-ci-failures' into 'master' Fix #470: Fix unit test issues on Ubuntu CI Closes #470 See merge request cmucl/cmucl!348 - - - - - 3 changed files: - bin/run-unit-tests.sh - tests/issues.lisp - + tests/test-run-prog/ls-link Changes: ===================================== bin/run-unit-tests.sh ===================================== @@ -41,11 +41,6 @@ done # Shift out the options shift $((OPTIND - 1)) -# Create the test directory needed by the issue.45 test. -rm -rf test-tmp -mkdir test-tmp -ln -s /bin/ls test-tmp/ls-link - # Set the timestamps on 64-bit-timestamp-2038.txt and # 64-bit-timestamp-2106.txt, but only for OSes where we know this # works. (This is so we don't an annoying error message from touch @@ -56,8 +51,9 @@ ln -s /bin/ls test-tmp/ls-link # tests/os.lisp. case `uname -s` in Linux) - touch -d "1 April 2038" tests/resources/64-bit-timestamp-2038.txt - touch -d "1 April 2106" tests/resources/64-bit-timestamp-2106.txt + # -t format is [[CC]YY]MMDDhhmm[.ss] + touch -t 203804010000 tests/resources/64-bit-timestamp-2038.txt + touch -t 210604010000 tests/resources/64-bit-timestamp-2106.txt ;; esac ===================================== tests/issues.lisp ===================================== @@ -436,7 +436,7 @@ (define-test issue.45 (:tag :issues) ;; This depends on run-tests to setup the test directory correctly! - (let* ((test-dir #p"test-tmp/") + (let* ((test-dir #p"tests/test-run-prog/") (test-dir-name (namestring test-dir))) (flet ((do-test (program) (with-output-to-string (s) ===================================== tests/test-run-prog/ls-link ===================================== @@ -0,0 +1,2 @@ +#! /bin/sh +exec /bin/ls "$@" View it on GitLab: https://gitlab.common-lisp.net/cmucl/cmucl/-/compare/9a4f3d7e2a513e6ef82112… -- View it on GitLab: https://gitlab.common-lisp.net/cmucl/cmucl/-/compare/9a4f3d7e2a513e6ef82112… You're receiving this email because of your account on gitlab.common-lisp.net.

1 0

[Git][cmucl/cmucl][issue-470-ubuntu-ci-failures] Remove commented-out code that's not needed anymore
by Raymond Toy (＠rtoy) 06 Feb '26

06 Feb '26

Raymond Toy pushed to branch issue-470-ubuntu-ci-failures at cmucl / cmucl Commits: f9130c5e by Raymond Toy at 2026-02-05T16:21:46-08:00 Remove commented-out code that's not needed anymore A left over from the previous implementation that has been changed. - - - - - 1 changed file: - bin/run-unit-tests.sh Changes: ===================================== bin/run-unit-tests.sh ===================================== @@ -41,11 +41,6 @@ done # Shift out the options shift $((OPTIND - 1)) -# Create the test directory needed by the issue.45 test. -#rm -rf test-tmp -#mkdir test-tmp -#ln -s /bin/ls test-tmp/ls-link - # Set the timestamps on 64-bit-timestamp-2038.txt and # 64-bit-timestamp-2106.txt, but only for OSes where we know this # works. (This is so we don't an annoying error message from touch View it on GitLab: https://gitlab.common-lisp.net/cmucl/cmucl/-/commit/f9130c5e347916c1996ffca… -- View it on GitLab: https://gitlab.common-lisp.net/cmucl/cmucl/-/commit/f9130c5e347916c1996ffca… You're receiving this email because of your account on gitlab.common-lisp.net.

1 0

[Git][cmucl/cmucl][issue-469-enable-cr-pow] 4 commits: Fix #470: Fix unit test issues on Ubuntu CI
by Raymond Toy (＠rtoy) 05 Feb '26

05 Feb '26

Raymond Toy pushed to branch issue-469-enable-cr-pow at cmucl / cmucl Commits: 3713015e by Raymond Toy at 2026-02-03T08:36:26-08:00 Fix #470: Fix unit test issues on Ubuntu CI For the timestamps, use `touch -t` to specify the time including hour and minutes. Previously, Ubuntu was using the time as 01:00:00 instead of the expected 00:00:00. Using `-t` makes it easy to read the expected time. On Ubuntu 25.10, you can't symlink to /bin/ls. It produces a security violation about the program name being incorrect. Instead define a simple shell script to run /bin/ls. - - - - - f141f493 by Raymond Toy at 2026-02-03T15:58:55-08:00 Just use a shell script for ls-link The attempt of linking ls-link to the actual location of /bin/ls doesn't work. Use a shell script instead. The script is in tests/test-run-prog which means issues.lisp needs to be informed of the new location. - - - - - 5d8c6845 by Raymond Toy at 2026-02-03T17:15:02-08:00 Forgot to add the ls-link script - - - - - dd6a4f9e by Raymond Toy at 2026-02-04T16:14:36-08:00 Merge branch 'issue-470-ubuntu-ci-failures' into issue-469-enable-cr-pow - - - - - 3 changed files: - bin/run-unit-tests.sh - tests/issues.lisp - + tests/test-run-prog/ls-link Changes: ===================================== bin/run-unit-tests.sh ===================================== @@ -42,9 +42,9 @@ done shift $((OPTIND - 1)) # Create the test directory needed by the issue.45 test. -rm -rf test-tmp -mkdir test-tmp -ln -s /bin/ls test-tmp/ls-link +#rm -rf test-tmp +#mkdir test-tmp +#ln -s /bin/ls test-tmp/ls-link # Set the timestamps on 64-bit-timestamp-2038.txt and # 64-bit-timestamp-2106.txt, but only for OSes where we know this ===================================== tests/issues.lisp ===================================== @@ -436,7 +436,7 @@ (define-test issue.45 (:tag :issues) ;; This depends on run-tests to setup the test directory correctly! - (let* ((test-dir #p"test-tmp/") + (let* ((test-dir #p"tests/test-run-prog/") (test-dir-name (namestring test-dir))) (flet ((do-test (program) (with-output-to-string (s) ===================================== tests/test-run-prog/ls-link ===================================== @@ -0,0 +1,2 @@ +#! /bin/sh +exec /bin/ls "$@" View it on GitLab: https://gitlab.common-lisp.net/cmucl/cmucl/-/compare/bd64e4c64e601124cd25a0… -- View it on GitLab: https://gitlab.common-lisp.net/cmucl/cmucl/-/compare/bd64e4c64e601124cd25a0… You're receiving this email because of your account on gitlab.common-lisp.net.

1 0