Project

General

Profile

Actions
Copy link

Feature #1139

closed

Let rcv create report when BLAST doesn't find any entry point

Added by Evgeny Novikov about 13 years ago. Updated about 13 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
Pavel Shved
Category:
Infrastructure
Start date:
04/26/2011
Due date:
% Done:

0%

Estimated time:
Published in build:

Description

At the moment all works:

rcv-blast: INFO: ...                                                                                   
BLAST couldn't find entry point/error location at /home/joker/work/14_driver/test_ldv_tools_2/bin/../dscv/rcv/blast line 387. 
rcv-blast: TRACE: Child's stdout stream closed.                                                                               
rcv-blast: TRACE: Child's stderr stream closed.                                                                               
rcv-blast: TRACE: BLAST open3 return value: 768                                                                               
rcv-blast: INFO: BLAST return value: 768                                                                                      
rcv-blast: TRACE: BLAST stats: utime 0.349946, stime 0.092985

and rcv creates empty report after all:
<reports/>

This leads to loss of the problem and statistics so it should be done better.

Related issues 1 (0 open — 1 closed)

Is duplicate of Linux Driver Verification - Bug #996: Entry point/error location should not trigger a fatal integration errorClosedPavel Shved03/29/201106/06/2011

Actions
Actions
Copy link
 #1

Updated by Evgeny Novikov about 13 years ago

Why does it contradict issue #996?..

Actions
Copy link
 #2

Updated by Pavel Shved about 13 years ago

  • Status changed from New to Rejected

Duplicates the issue #996 that actually evolved as the time went... :)

Actions
Copy link

Also available in: Atom PDF