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
ERR_OPENDIR if there was a transient error, e.g. the output file is on a network volume that is not available. The validator will try this result again later.
Same functionality does not seem to be available in the script_validator code. Returning -111 from the init_script results in the result being marked as invalid, and the workunit returns to unvalidated state and sends out a new result.
Steps To Reproduce
create a basic validator script that returns an error value, e.g.
#!/usr/bin/php
exit(-111); // ERR_OPENDIR
run the validator as an init script.
Expected behavior
Validation does not complete, result is not marked as valid, workunit is not marked as valid.
The text was updated successfully, but these errors were encountered:
@davidpanderson I think invalid result state now got broken. My validator is now running in a loop on a result that should be marked as invalid (I exit(42), also tried other nonzero values too):
Describe the bug
Documentation at https://github.com/BOINC/boinc/wiki/Validators-in-C states that C++ validator can handle specific return values, such as:
Same functionality does not seem to be available in the script_validator code. Returning -111 from the init_script results in the result being marked as invalid, and the workunit returns to unvalidated state and sends out a new result.
Steps To Reproduce
Expected behavior
Validation does not complete, result is not marked as valid, workunit is not marked as valid.
The text was updated successfully, but these errors were encountered: