Joe Schmid
08/19/2021, 8:30 PMJoe Schmid
08/19/2021, 8:32 PM16:21:50
INFO
CloudTaskRunner
Task 'train_test_track[15]': Starting task run...
16:21:50
INFO
CloudTaskRunner
FeatureSpace metadata saved to: /home/efs/featurespace/data/XXXXXXXX/metadata/XXXXXX
FeatureSet data within batch folder: XXXXXXXX
16:21:52
INFO
CloudTaskRunner
Task 'train_test_track[15]': Finished task run for task with final state: 'TimedOut'
Obviously, the last log entry is only 2 seconds after the first, which seems like not much time for anything to time out. 🙂Chris White
Joe Schmid
08/19/2021, 8:37 PMJoe Schmid
08/19/2021, 8:38 PMJoe Schmid
08/19/2021, 8:42 PMtags=["dask-resource:CPU=1"]
Chris White
TimeoutError
s from tasks are converted to TimedOut
states, not just those that use prefect timeouts: https://github.com/PrefectHQ/prefect/blob/0.13.19/src/prefect/engine/task_runner.py#L864-L868
In newer versions, `TimeoutError`s convert to standard Failed
states, and only Prefect-speciifc timeouts result in TimedOut
states
So this suggests to me that something in this task is raising a TimeoutError
really quickly and Prefect is capturing that and misinterpreting itJoe Schmid
08/19/2021, 8:46 PMChris White