Skip to content

Commit f49dc96

Browse files
committed
Doc(aws): Add notes about incomplete jobs, failure reason
1 parent 3ce705d commit f49dc96

1 file changed

Lines changed: 7 additions & 0 deletions

File tree

aws/README.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -58,6 +58,10 @@ Without the logs you will only see job status, runtime etc.
5858
The best way to find failures is to either select those with the `Failed` status,
5959
or with `Succeeded` but `Incomplete rounds`.
6060

61+
When you believe that something has failed because it doesn't have all rounds completed,
62+
make sure to check the s3 folder for the presence of logs (else there might be a missing sync
63+
so the viewer doesn't have the most recent completed rounds).
64+
6165
Proceed as follows:
6266

6367
1. Select them all
@@ -68,6 +72,9 @@ Proceed as follows:
6872

6973
Now you've resubmitted them and removed the partial run S3 folders.
7074

75+
You can also still investigate the failure reason with the AWS console.
76+
In the log viewing window, select sorting -> Desc., then click `Filter logs`.
77+
7178
## Setup
7279

7380
* `setup/`: Everything needed to set up AWS to run codeclash jobs. Advanced user stuff.

0 commit comments

Comments
 (0)