Project

General

Profile

Actions

Bug #996

closed

Entry point/error location should not trigger a fatal integration error

Added by Pavel Shved over 13 years ago. Updated over 13 years ago.

Status:
Closed
Priority:
High
Assignee:
Category:
Infrastructure
Start date:
03/29/2011
Due date:
06/06/2011
% Done:

0%

Estimated time:
Detected in build:
svn
Platform:
Published in build:
63930e7c

Description

When BLAST does not find entry point or error location, it exits with return code 3, and this triggers an integration error, which makes everything fail.

Perhaps, it was necessary half a year ago, but as our infrastructure matured it became more of a local issue than a mistake in integrating the components together (see, for instance, bug #416). Today it could just be listed as a problem of RCV or DSCV. I suggest to list it as RCV problem, as it may be related to "parse errors" and conversion of a program into CFG form.


Related issues 1 (0 open1 closed)

Has duplicate Linux Driver Verification - Feature #1139: Let rcv create report when BLAST doesn't find any entry pointRejectedPavel Shved04/26/2011

Actions
Actions

Also available in: Atom PDF