gregandClaude Opus 5.5
65cbb8cfd4
First boot with the install fix ran ARK for ~10 minutes and found, in ShooterGame.log: "Server: ... has successfully started!", "EOS ownership validation initialized: Success", "Full Startup: 36.26 seconds" and, about two minutes later, "Server has completed startup and is now advertising for join. (9.96GB Mem)". That last line is when players, console players through EOS included, can join, so it is the readyPattern; the real line is test.yaml's readyExample. Boot tests now wait for it instead of only checking ARK stays up for 10 minutes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
7 lines
464 B
YAML
7 lines
464 B
YAML
# yaml-language-server: $schema=../../schema/test.schema.json
|
|
# Values CI uses to boot-test this game. Never put real credentials here: map them under 'secrets'.
|
|
# Ready means advertising for join, which comes about 2 minutes after "Full Startup"; the first boot also
|
|
# installs ~13 GB and Proton, so the timeout is generous.
|
|
readyExample: '[2026.10.25-06.32.24:246][239]Server has completed startup and is now advertising for join. (9.96GB Mem)'
|
|
timeoutSec: 2400
|