Verification run
Run 339
failedcommit
71ef5dc5e76dtoolchain lean-v4-30-0prover leantook 3h 44m · finished 14w agoruntime execution failed: error returned from database: total size of jsonb object elements exceeds the maximum of 268435455 bytes
Semantic extraction
Modules done20 / 21
Remaining1
Path-
Timeout left-
20 succeeded attempts · 1 failed attempts
Module attempts
| Batch | Status | Failure | Modules | Max duration | Latest finish |
|---|---|---|---|---|---|
extract-batch-00020 | succeeded | none | 1 | 1h 39m | |
extract-batch-00019 | succeeded | none | 1 | 6m 9s | |
extract-batch-00018 | succeeded | none | 1 | 31m 27s | |
extract-batch-00017 | succeeded | none | 1 | 5m 46s | |
extract-batch-00016 | succeeded | none | 1 | 5m 3s | |
extract-batch-00015 | succeeded | none | 1 | 4m 47s | |
extract-batch-00014 | succeeded | none | 1 | 4m 57s | |
extract-batch-00013 | succeeded | none | 1 | 2m 5s | |
extract-batch-00012 | succeeded | none | 1 | 2m 1s | |
extract-batch-00011 | succeeded | none | 1 | 26s | |
extract-batch-00010 | succeeded | none | 1 | 2m 2s | |
extract-batch-00009 | succeeded | none | 1 | 2m 3s | |
extract-batch-00008 | succeeded | none | 1 | 2m 20s | |
extract-batch-00007 | failed | semantic extract failed | 1 | 2s | |
extract-batch-00006 | succeeded | none | 1 | 7m 41s | |
extract-batch-00005 | succeeded | none | 1 | 2m 0s | |
extract-batch-00004 | succeeded | none | 1 | 1m 52s | |
extract-batch-00003 | succeeded | none | 1 | 1m 56s | |
extract-batch-00002 | succeeded | none | 1 | 2m 23s | |
extract-batch-00001 | succeeded | none | 1 | 5m 6s | |
extract-batch-00000 | succeeded | none | 1 | 5m 1s |
Workflow timeline
1 workflow- build verificationfailedstarted finished
- verifyfailed
runtime execution failed: error returned from database: total size of jsonb object elements exceeds the maximum of 268435455 bytes
Attempts
- failed#1
- persist resultsucceeded
Attempts
- succeeded#1
- complete jobsucceeded
Attempts
- succeeded#1
Github checks
No Github check run linked yet. This appears when the repository is Github-connected and the worker has published queue, running, and completion check updates.