end-to-end/actions/feature-logs-compression/run.sh

#!/bin/bash

set -e

source $FEATURE_DIR/../../lib/lib.sh
source $FEATURE_DIR/../../forgejo/fixtures.sh

if ! retry bash -c "find $DIR/forgejo-work-path/data/actions_log/root/example-echo | grep --quiet log.zst"; then
    (
        cd $DIR/forgejo-work-path
        find data
    )
    echo expected a single log.zst file in data/actions_log/root/example-echo
    exit 1
fi
actions: verify the log compression feature If running Forgejo >= v9.0, verify the logs are compressed by default 2024-08-11 11:38:52 +02:00			`#!/bin/bash`

			`set -e`

			`source $FEATURE_DIR/../../lib/lib.sh`
			`source $FEATURE_DIR/../../forgejo/fixtures.sh`

actions: fix: wait for the action logs to show up The Forgejo instance completed the echo test successfully, there must be a log at some point. But since Forgejo is still running, it may not had time to write the logs just yet. Retry instead of giving up immediately. 2024-11-12 15:40:12 +01:00			`if ! retry bash -c "find $DIR/forgejo-work-path/data/actions_log/root/example-echo \| grep --quiet log.zst"; then`
actions: feature: compression: do not hardcode the log path The log path depends on the previous actions run and may not always be 01/1.log.zst. Assuming it is makes this test fragile as it is influenced by which previous tests are run and what they do. 2024-08-23 16:19:22 +02:00			`(`
			`cd $DIR/forgejo-work-path`
			`find data`
			`)`
			`echo expected a single log.zst file in data/actions_log/root/example-echo`
			`exit 1`
			`fi`