ci : set GITHUB_ACTIONS to true for server tests

[danbev]

This commit tries to address an issue with the server tests which are failing with a timeout. Looking at the logs it seems like they are timing out after 12 seconds:

FAILED unit/test_chat_completion.py::test_completion_with_json_schema[False-json_schema0-6-"42"] - TimeoutError: Server did not start within 12 seconds

This is somewhat strange as in utils.py we have the following values:

DEFAULT_HTTP_TIMEOUT = 12

if "LLAMA_SANITIZE" in os.environ or "GITHUB_ACTION" in os.environ:
    DEFAULT_HTTP_TIMEOUT = 30

    def start(self, timeout_seconds: int | None = DEFAULT_HTTP_TIMEOUT) -> None:

It should be the case that a test running in a github action should have a timeout of 30 seconds. However, it seems like this is not the case. Inspecting the logs from the CI job we can see the following environment variables:

Run cd examples/server/tests
2 cd examples/server/tests
3 ./tests.sh
4 shell: /usr/bin/bash -e {0}
5 env:
6 LLAMA_LOG_COLORS: 1
7 LLAMA_LOG_PREFIX: 1
8 LLAMA_LOG_TIMESTAMPS: 1
9 LLAMA_LOG_VERBOSITY: 10
10 pythonLocation: /opt/hostedtoolcache/Python/3.11.11/x64

[ngxson]

My coworkers at HF also reporting some abnormal timeout on other projects, so probably wait for a bit more to see if it's get fixed.

Re. GITHUB_ACTIONS env, yes it's missing because it must by specified in env: section of the step in workflow, you can add somthing like:

env:
  GITHUB_ACTIONS: "true"

[danbev]

My coworkers at HF also reporting some abnormal timeout on other projects, so probably wait for a bit more to see if it's get fixed.

Thanks for that, good to know!
So this might not actually help depending on the underlying issue but might still be worth to have the timeout a little longer.