Different error codes for Tuist errors

Ideas
1

We run a lot of Tuist builds and tests on CI, so we tend to get a bunch of failures whenever there’s a dip in availability. We’re thinking of enhancing our CI script to run tests a second time without the binary cache if it fails with it. But to do that effectively we would need to be able to distinguish between a tuist test failure due to downloading cached binaries or selective test results, vs. an actual test failure.

One idea would be to support different return codes from Tuist. Would that work, is there another option we could use, or is this already supported and I missed it?

2

I believe the better option here instead of using specific exit codes is to morph cache unavailability errors into warnings. What errors triggered this post?

We can either:

  • Turn any cache-related error into a warning
  • Turn errors that we know are due to unavailability into warnings

I’d rather try to do the latter – there are errors such as when a TUIST_PROJECT_TOKEN is missing on the CI that I’d like to still keep as errors.

I’d propose that you flag any unavailability error that caused your pipelines to fail and we’ll make sure to handle it.

3

I like your idea better. In this case it was:

Received a session error when sending GET request to https://tuist-storage-prod.fly.storage.tigris.dev/<redacted>: <NSHTTPURLResponse: 0x6000039d5a20> { URL: https://tuist-storage-prod.fly.storage.tigris.dev/<redacted> } { Status Code: 403, Headers {
    "Content-Length" =     (
        343
    );
    "Content-Type" =     (
        "application/xml"
    );
    Date =     (
        "Thu, 12 Dec 2024 14:38:06 GMT"
    );
    Server =     (
        "Tigris OS"
    );
    "Strict-Transport-Security" =     (
        "max-age=6307****; includeSubDomains; preload"
    );
    "server-timing" =     (
        "total;dur=50,cache;desc=miss;dur=4, server;desc=miss;dur=7"
    );
    "x-amz-request-id" =     (
        1734014286031322053
    );
} }
Consider creating an issue using the following link: https://github.com/tuist/tuist/issues/new/choose

Exited with code exit status 1
4

Thanks!

I raised an issue for this, we hope to get to this soon.