Bug #9067
closedKlever fails with corrupted
0%
Description
An inner component fails while processing witnesses and nevertheless Klever prepares an unsafe report. As there are no witnesses then it fails with 'corrupted' and stops the launch completely.
[Reporter] Raise exception:
Traceback (most recent call last):
File "/home/debian/klever-inst/klever/core/core/components.py", line 428, in run
self.main()
File "/home/debian/klever-inst/klever/core/core/components.py", line 332, in callbacks_caller
ret = attr(*args, **kwargs)
File "/home/debian/klever-inst/klever/core/core/core.py", line 304, in send_reports
self.session.upload_report(report_file, report_file_archives)
File "/home/debian/klever-inst/klever/core/core/session.py", line 149, in upload_report
self.__upload_archive('reports/upload/', {'report': report}, archives)
File "/home/debian/klever-inst/klever/core/core/session.py", line 187, in __upload_archive
for archive in archives], stream=True)
File "/home/debian/klever-inst/klever/core/core/session.py", line 93, in __request
'Got error "{0}" when send "{1}" request to "{2}"'.format(self.error, method, url))
core.session.BridgeError: Got error "There are no error traces in report" when send "POST" request to "http://localhost:8998/reports/upload/"
Traceback (most recent call last):
File "/home/debian/klever-inst/klever/core/core/core.py", line 91, in main
'coverage_finished': multiprocessing.Manager().dict()
File "/home/debian/klever-inst/klever/core/core/job.py", line 110, in start_jobs
core.components.launch_workers(core_obj.logger, [job], subcomponents + [core_obj.uploading_reports_process])
File "/home/debian/klever-inst/klever/core/core/components.py", line 199, in launch_workers
check_components(logger, monitoring_list)
File "/home/debian/klever-inst/klever/core/core/components.py", line 304, in check_components
mc.join()
File "/home/debian/klever-inst/klever/core/core/components.py", line 332, in callbacks_caller
ret = attr(*args, **kwargs)
File "/home/debian/klever-inst/klever/core/core/components.py", line 546, in join
raise ComponentError('Component "{0}" failed'.format(self.name))
core.components.ComponentError: Component "Reporter" failed
Updated by Evgeny Novikov almost 6 years ago
- Category set to Results processing
- Assignee set to Evgeny Novikov
- Priority changed from Normal to Immediate
Updated by Evgeny Novikov almost 6 years ago
- Related to Feature #8705: Change the way of reporting unsafe reports added
Updated by Evgeny Novikov almost 6 years ago
- Status changed from New to Resolved
- Target version set to 1.1
I trivially fixed the issue in branch fix-9067. Wait for testing results.
Updated by Evgeny Novikov almost 6 years ago
- Status changed from Resolved to Closed
Tests passed. Moreover, Pavel reported that a job that has status Corrupted before now finishes well. I merged the branch to master in c116c448 and backported the bug fix to branch v1.0-stable.