testing: more resilient resultchecker.py

Don't assume that each server actually has an entry in the result
list. In case of a failure to write that, treat the server as failed
to highlight the problem instead of failing in the resultchecker.py
script.
This commit is contained in:
Patrick Ohly 2014-02-02 18:55:57 +01:00
parent 73e061f81a
commit 88ac5872a5
1 changed files with 7 additions and 2 deletions

View File

@ -310,8 +310,13 @@ def step2(resultdir, result, servers, indents, srcdir, shellprefix, backenddir):
indents.append(indent)
result.write(indent+'<'+server+' path="' +rserver+'" ')
#valgrind check resutls
if(params[server].find('return code ') !=-1):
result.write('result="'+params[server].partition('return code ')[2].partition(')')[0]+'" ')
if not params.get(server, None):
# Unknown result, treat as failure.
result.write('result="1"')
else:
m = re.search(r'return code (\d+)', params[server])
if m:
result.write('result="%s"' % m.group(1))
result.write('>\n')
# sort files by creation time, to preserve run order
logs = map(lambda file: (os.stat(file).st_mtime, file),