very fast (0/0) MAYBEs (starexec SQL error?)

[jwaldmann]

Note: this issue is about job pairs that fail immediately, see https://www.tapatalk.com/groups/starexec/job-pair-killed-immediately-setting-up-cpuset-cgro-t141.html

There is another error about job pairs that time out after 5 minutes, but are still reported as having used 0 seconds. These issues need to be separated.

https://termcomp.imn.htwk-leipzig.de/pairs/303184990

Note:

08/06/17 09:09:26 AM CDT: mysql -u... -p... -h starexec2.star.cs.uiowa.edu prod_starexec -e "CALL UpdatePairRunSolverStats(303184990, 'n123.star.cs.uiowa.edu', , , 0, 0, , 0, 1, 4331)"
ERROR 1064 (42000) at line 1: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near ' , 0, 0, , 0, 1, 4331)' at line 1
08/06/17 09:09:26 AM CDT: Error copying stats from watchfile into database. Copying varfile to log {
08/06/17 09:09:26 AM CDT: } End varfile.
08/06/17 09:09:26 AM CDT: Copying watchfile to log {
08/06/17 09:09:26 AM CDT: } End watchfile.

[jwaldmann]

if starexec cannot solve this (in time), then we could work around by ignoring (for scoring) all benchmarks where such an error occured.

It may be a good idea anyway to split the results tables in a part that's "done" and a part that's not.