Actions
Bug #8268
closedNativeScheduler fails when swap is enabled and kernel parameter swapaccount is 1
Status:
Rejected
Priority:
Immediate
Assignee:
-
Category:
Scheduling
Target version:
-
Start date:
07/03/2017
Due date:
% Done:
0%
Estimated time:
Detected in build:
svn
Platform:
Published in build:
Description
The corresponding error log looks like:
"/home/novikov/work/benchexec/bin/benchexec" outputted to STDERR:
2017-07-03 13:59:56,051 - WARNING - System has swapped during benchmarking. Benchmark results are unreliable!
"/home/novikov/work/benchexec/bin/benchexec" outputted to STDERR:
2017-07-03 13:59:56,186 - WARNING - System has swapped during benchmarking. Benchmark results are unreliable!
Traceback (most recent call last):
File "/home/novikov/work/klever/scheduler/client/__init__.py", line 104, in run_benchexec
exit_code = solve(logger, conf, mode, server)
File "/home/novikov/work/klever/scheduler/client/__init__.py", line 137, in solve
return solve_task(logger, conf, server)
File "/home/novikov/work/klever/scheduler/client/__init__.py", line 171, in solve_task
os._exit(int(exit_code))
TypeError: int() argument must be a string, a bytes-like object or a number, not 'NoneType'
After that very strange verification results are reported.
The issue is important since it can happen due to other reasons causing BenchExec warnings.
Updated by Evgeny Novikov over 6 years ago
- Status changed from New to Rejected
- Assignee deleted (
Ilja Zakharov)
I don't see the issue anymore. Most likely the encountered issue wasn't related with swapping at all. And it was fixed within another bug fix.
Actions