glib/.gitlab-ci/show-execution-environment.sh

#!/bin/bash

set -eux -o pipefail

id || :
capsh --print || :
env -0 | sort -z | perl -pe 's/\0/\n/g' || :
setpriv --dump || :
ulimit -a || :
cat /proc/self/status || :
cat /proc/self/mountinfo || :
stat /etc/machine-id || :
stat /var/lib/dbus/machine-id || :
CI: Show execution environment before we start This will help to debug CI issues that are related to us running in a container that might have unusual capabilities, mount points, filesystems etc., such as (probably) #2027, #2028, #2029. Signed-off-by: Simon McVittie <smcv@collabora.com> 2020-02-12 15:35:54 +01:00			`#!/bin/bash`

			`set -eux -o pipefail`

			`id \|\| :`
			`capsh --print \|\| :`
			`env -0 \| sort -z \| perl -pe 's/\0/\n/g' \|\| :`
			`setpriv --dump \|\| :`
			`ulimit -a \|\| :`
			`cat /proc/self/status \|\| :`
			`cat /proc/self/mountinfo \|\| :`
ci: Include details of machine ID in CI output Include the size of the `machine-id` file, but not the value itself as that is sensitive for non-throwaway machines. What’s most useful for debugging CI problems is knowing whether, and where, the `machine-id` is set. Signed-off-by: Philip Withnall <pwithnall@endlessos.org> 2021-03-01 14:54:09 +01:00			`stat /etc/machine-id \|\| :`
			`stat /var/lib/dbus/machine-id \|\| :`