Actions
Bug #7848
closedCan't see lists of unsafes
Start date:
01/12/2017
Due date:
01/12/2017
% Done:
100%
Estimated time:
Detected in build:
svn
Platform:
Published in build:
Description
After Bridge optimizations one can't see lists of unsafes:
Internal Server Error: /reports/component/1/unsafes/5/ Traceback (most recent call last): File "/usr/local/lib/python3.4/dist-packages/django/core/handlers/exception.py", line 39, in inner response = get_response(request) File "/usr/local/lib/python3.4/dist-packages/django/core/handlers/base.py", line 249, in _legacy_get_response response = self._get_response(request) File "/usr/local/lib/python3.4/dist-packages/django/core/handlers/base.py", line 187, in _get_response response = self.process_exception_by_middleware(e, request) File "/usr/local/lib/python3.4/dist-packages/django/core/handlers/base.py", line 185, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/local/lib/python3.4/dist-packages/django/contrib/auth/decorators.py", line 23, in _wrapped_view return view_func(request, *args, **kwargs) File "/var/www/bridge/reports/views.py", line 231, in report_list_by_verdict return report_list(request, report_id, ltype, verdict=verdict) File "/usr/local/lib/python3.4/dist-packages/django/contrib/auth/decorators.py", line 23, in _wrapped_view return view_func(request, *args, **kwargs) File "/var/www/bridge/bridge/utils.py", line 118, in wait res = f(*args, **kwargs) File "/var/www/bridge/reports/views.py", line 196, in report_list component_id=component_id, verdict=verdict, tag=tag, problem=problem, mark=mark, attr=attr File "/var/www/bridge/reports/utils.py", line 117, in __init__ self.table_data = self.__get_table_data() File "/var/www/bridge/reports/utils.py", line 162, in __get_table_data self.columns, values = actions[self.type]() File "/var/www/bridge/reports/utils.py", line 436, in __unsafes_data val = get_user_time(self.user, parent_cpus[reports[rep_id]['parent_id']]) File "/var/www/bridge/jobs/utils.py", line 584, in get_user_time converted = convert_time(int(milliseconds), user.extended.accuracy) TypeError: int() argument must be a string or a number, not 'NoneType'
Updated by Evgeny Novikov over 7 years ago
Perhaps after that the server crashed so the job decision hung:
2017/01/12 15:28:59 [error] 454#0: *8588 upstream prematurely closed connection while reading response header from upstream, client: 127.0.0.1, server: 127.0.0.1, request: "POST /service/get_jobs_and_tasks/ HTTP/1.1", upstream: "http://unix:/var/www/bridge/bridge.sock:/service/get_jobs_and_tasks/", host: "localhost:8998" 2017/01/12 15:29:44 [error] 454#0: *9363 upstream prematurely closed connection while reading response header from upstream, client: 127.0.0.1, server: 127.0.0.1, request: "POST /reports/upload/ HTTP/1.1", upstream: "http://unix:/var/www/bridge/bridge.sock:/reports/upload/", host: "localhost:8998" 2017/01/12 15:30:14 [error] 454#0: *8430 upstream prematurely closed connection while reading response header from upstream, client: 127.0.0.1, server: 127.0.0.1, request: "POST /service/get_jobs_and_tasks/ HTTP/1.1", upstream: "http://unix:/var/www/bridge/bridge.sock:/service/get_jobs_and_tasks/", host: "localhost:8998" 2017/01/12 15:32:20 [error] 454#0: *9910 upstream prematurely closed connection while reading response header from upstream, client: 10.10.2.157, server: 127.0.0.1, request: "GET /reports/component/1/unknowns/2/ HTTP/1.1", upstream: "http://unix:/var/www/bridge/bridge.sock:/reports/component/1/unknowns/2/", host: "10.10.17.116:8998", referrer: "http://10.10.17.116:8998/jobs/3/" 2017/01/12 15:32:24 [error] 454#0: *10725 upstream prematurely closed connection while reading response header from upstream, client: 10.10.2.157, server: 127.0.0.1, request: "GET /reports/component/1/unknowns/37/ HTTP/1.1", upstream: "http://unix:/var/www/bridge/bridge.sock:/reports/component/1/unknowns/37/", host: "10.10.17.116:8998", referrer: "http://10.10.17.116:8998/jobs/3/"
Updated by Vladimir Gratinskiy over 7 years ago
- Due date set to 01/12/2017
- Status changed from New to Resolved
- % Done changed from 0 to 100
I think this exception is happens when all these conditions are satisfied:
1) the job is light;
2) the job status is "In progress";
3) There are no archives uploaded for verification report which is parent of unsafe (so, there are no logs for light jobs?);
So the parent of unsafe is Core, which is not finished yet and does not have cpu_time.
It is fixed in branch fix_7848.
Updated by Evgeny Novikov over 7 years ago
- Status changed from Resolved to Closed
Yes, you are totally right. So nobody met all these conditions before. The fix works and I merged the branch to master in e0fcc11.
Actions