Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Transient Engine Test Failure: S3.get_object "Read timed out" #9112

Open
mwu-tow opened this issue Feb 20, 2024 · 0 comments
Open

Transient Engine Test Failure: S3.get_object "Read timed out" #9112

mwu-tow opened this issue Feb 20, 2024 · 0 comments
Labels

Comments

@mwu-tow
Copy link
Contributor

mwu-tow commented Feb 20, 2024

We had AWS_Tests fail with the following:

[FAILED] S3.get_object: [1/2, 76167ms]
    - [FAILED] should be able to get an object [76163ms]
        Reason: An unexpected dataflow error ((S3_Error.Error 'An IO error has occurred: java.net.SocketTimeoutException: Read timed out' 's3://enso-data-samples/Bus_Stop_Benches.geojson')) has been matched (at /runner/_work/enso/enso/test/AWS_Tests/src/S3_Spec.enso:136:13-50).
        at <enso> <anonymous>(/runner/_work/enso/enso/built-distribution/enso-engine-2024.1.1-dev-linux-amd64/enso-2024.1.1-dev/lib/Standard/AWS/2024.1.1-dev/src/S3/S3.enso:205:9-110)
        at <enso> Panic.catch(Internal)

See the full log: https://github.com/enso-org/enso/actions/runs/7971892171/job/21762512548#step:8:5319
Archived: logs_116156.zip

If the test relies on external networking operations, we should consider adding retries or some other way of dealing with a random connectivity problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: New
Development

No branches or pull requests

1 participant