You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, if there are errors in one of the results directories from the runDDTests option, the files are skipped.
With the ETL process, we can now ingest the errors as well and produce a Failed report.
The restore option should be adjusted to detect when there are errors, and then pick up the relevant files and post them as Failed tests.
There are a few cases here:
All required files are present but there was an error. Usually there will be an error.log in this scenario. In general, if there's an error.log then there was an error, even if it's 0 length.
Not all required files are present, but there's still an error.log file. In this scenario, the utils need to figure out which required files weren't there and detect what failed, then create a request to handle this accordingly.
Not all required files are present, but there's no error.log file. In this case, the error step can be determined by detecting which required files are not present.
Cert Utils skips the error scenario and logs it in the terminal presently:
Currently, if there are errors in one of the results directories from the
runDDTests
option, the files are skipped.With the ETL process, we can now ingest the errors as well and produce a Failed report.
The
restore
option should be adjusted to detect when there are errors, and then pick up the relevant files and post them as Failed tests.There are a few cases here:
error.log
in this scenario. In general, if there's an error.log then there was an error, even if it's 0 length.error.log
file. In this scenario, the utils need to figure out which required files weren't there and detect what failed, then create a request to handle this accordingly.error.log
file. In this case, the error step can be determined by detecting which required files are not present.Cert Utils skips the error scenario and logs it in the terminal presently:
It also provides the reason for the error usually.
This should be a library method that can be called from the Certification backend as well as the Cert Utils CLI.
The text was updated successfully, but these errors were encountered: