fish-shell/docker/context/fish_run_tests.sh

#!/bin/bash

# This script is copied into the root directory of our Docker tests.
# It is the entry point for running Docker-based tests.

cd ~/fish-build
git config --global --add safe.directory /fish-source
cmake -G Ninja -DCMAKE_BUILD_TYPE=Debug /fish-source "$@"

# Spawn a shell if FISH_RUN_SHELL_BEFORE_TESTS is set.
if test -n "$FISH_RUN_SHELL_BEFORE_TESTS"
then
    bash -i || exit
fi

ninja && ninja fish_run_tests
RES=$?

# Drop the user into a shell if FISH_RUN_SHELL_AFTER_TESTS is set.
if test -n "$FISH_RUN_SHELL_AFTER_TESTS"; then
    bash -i
fi

exit $RES
Introduce Docker-based build and test environments This is the start of an effort to make it easier to build and run tests in various Linux environments. The idea is to reduce our reliance on CI and also allow an easy to way capture tricky environments like musl or gcc 5. This adds two initial Dockerfiles corresponding to Ubuntu Bionic, and Ubuntu Bionic with Thread Sanitizer enabled. It also adds a new script `docker/docker_run_tests.sh`. An example of usage: docker/docker_run_tests.sh docker/bionic-tsan.Dockerfile When run, this builds a Docker image (which is cached after the first build) and sets its entry point to a new script `fish_run_tests.sh`. It then launches a container with that image, with a directory `/fish-source` bound to the fish-shell source directory on the host. Note it is a bind mount, not a copy, so changes to host files are instantly visible inside the container. It then configures with CMake and runs the tests. The Docker user is `fishuser` with password `fish`. The script also supports two arguments `--shell-before` and `--shell-after`. These drop the user into a bash shell before (or after) the tests are run, to aid in debugging. Note there's no automation for invoking this script yet; it must be run manually. But it runs on both Mac and Linux! 2020-11-22 05:55:15 +08:00			`#!/bin/bash`

			`# This script is copied into the root directory of our Docker tests.`
			`# It is the entry point for running Docker-based tests.`

			`cd ~/fish-build`
Fix test_version.fish for Ubuntu Noble Numbat Docker build git_version_gen fails on Noble Numbat because modern Git refuses to read repo-local config if owned by another user. fishuser@a4263f53c93e:~/fish-build$ cd /fish-source/ fishuser@a4263f53c93e:/fish-source$ git describe --always --dirty fatal: detected dubious ownership in repository at '/fish-source' To add an exception for this directory, call: Allow reading it (though that doesn't seem necessary here, it would be better to ignore it). 2024-04-28 16:27:29 +08:00			`git config --global --add safe.directory /fish-source`
Ubuntu ASAN Dockerfile 2024-01-12 19:18:27 +08:00			`cmake -G Ninja -DCMAKE_BUILD_TYPE=Debug /fish-source "$@"`
Introduce Docker-based build and test environments This is the start of an effort to make it easier to build and run tests in various Linux environments. The idea is to reduce our reliance on CI and also allow an easy to way capture tricky environments like musl or gcc 5. This adds two initial Dockerfiles corresponding to Ubuntu Bionic, and Ubuntu Bionic with Thread Sanitizer enabled. It also adds a new script `docker/docker_run_tests.sh`. An example of usage: docker/docker_run_tests.sh docker/bionic-tsan.Dockerfile When run, this builds a Docker image (which is cached after the first build) and sets its entry point to a new script `fish_run_tests.sh`. It then launches a container with that image, with a directory `/fish-source` bound to the fish-shell source directory on the host. Note it is a bind mount, not a copy, so changes to host files are instantly visible inside the container. It then configures with CMake and runs the tests. The Docker user is `fishuser` with password `fish`. The script also supports two arguments `--shell-before` and `--shell-after`. These drop the user into a bash shell before (or after) the tests are run, to aid in debugging. Note there's no automation for invoking this script yet; it must be run manually. But it runs on both Mac and Linux! 2020-11-22 05:55:15 +08:00
			`# Spawn a shell if FISH_RUN_SHELL_BEFORE_TESTS is set.`
			`if test -n "$FISH_RUN_SHELL_BEFORE_TESTS"`
			`then`
			`bash -i \|\| exit`
			`fi`

Use new fish_run_tests target in Dockerfiles This fixes the Xenial Dockerfile and perhaps others. 2021-11-27 05:13:08 +08:00			`ninja && ninja fish_run_tests`
Correct exit status of fish_run_tests.sh fish_run_tests.sh was failing because its final command was a variable test which was usually false. Switch to an if statement so the result is true. 2022-10-24 01:13:52 +08:00			`RES=$?`
Introduce Docker-based build and test environments This is the start of an effort to make it easier to build and run tests in various Linux environments. The idea is to reduce our reliance on CI and also allow an easy to way capture tricky environments like musl or gcc 5. This adds two initial Dockerfiles corresponding to Ubuntu Bionic, and Ubuntu Bionic with Thread Sanitizer enabled. It also adds a new script `docker/docker_run_tests.sh`. An example of usage: docker/docker_run_tests.sh docker/bionic-tsan.Dockerfile When run, this builds a Docker image (which is cached after the first build) and sets its entry point to a new script `fish_run_tests.sh`. It then launches a container with that image, with a directory `/fish-source` bound to the fish-shell source directory on the host. Note it is a bind mount, not a copy, so changes to host files are instantly visible inside the container. It then configures with CMake and runs the tests. The Docker user is `fishuser` with password `fish`. The script also supports two arguments `--shell-before` and `--shell-after`. These drop the user into a bash shell before (or after) the tests are run, to aid in debugging. Note there's no automation for invoking this script yet; it must be run manually. But it runs on both Mac and Linux! 2020-11-22 05:55:15 +08:00
			`# Drop the user into a shell if FISH_RUN_SHELL_AFTER_TESTS is set.`
Correct exit status of fish_run_tests.sh fish_run_tests.sh was failing because its final command was a variable test which was usually false. Switch to an if statement so the result is true. 2022-10-24 01:13:52 +08:00			`if test -n "$FISH_RUN_SHELL_AFTER_TESTS"; then`
			`bash -i`
			`fi`

			`exit $RES`