-
Notifications
You must be signed in to change notification settings - Fork 121
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
ACHILLES_RESULTS table: ERROR: no runtime found in log file #745
Comments
The error occurs when we run Achilles with the output folder not being empty. |
Hi @apopassias, did it work with an empty achilles output folder? It might have something to do with Achilles appending to an existing log file, but I could not replicate this myself. |
Yes it works with an empty output folder.
…On Fri, Apr 5, 2024, 20:16 Maxim Moinat ***@***.***> wrote:
Hi @apopassias <https://github.com/apopassias>, did it work with an empty
achilles output folder? It might have something to do with Achilles
appending to an existing log file, but I could not replicate this myself.
—
Reply to this email directly, view it on GitHub
<#745 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BC2PLM7Q3ZW5XGEZQCM4U3DY33L5HAVCNFSM6AAAAAA72ZC2ACVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBQGI4DONRRHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
There are a few issues that occur with the log file. If the string search fails we can see errors or in the case like this with an existing log. Part of the 2.0 rewrite of Achilles will include a totally revamped logging table for runtime. |
In the ACHILLES_RESULT table there are entries for each analysis with id=2000000+analysis_id to store the execution time of each analysis in the column STRATUM_1.
These are to be used by cdmInpection to generate the reference document.
All of these records have STRATUM_1 values equal to "ERROR: no runtime found in log".
Any suggestions?
The text was updated successfully, but these errors were encountered: