| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] |
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0000252 | Rosetta | [All Projects] Input Handling | public | 2013-04-22 19:58 | 2013-04-22 23:06 |
|
| Reporter | rmoretti | |
| Assigned To | | |
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | new | Resolution | open | |
| Platform | | OS | | OS Version | |
| Product Version | Trunk | |
| Fixed in Version | | |
|
| Summary | 0000252: Issues with error message reporting (resfiles) |
| Description | If you have an error in a resfiles, Rosetta apparently no longer prints out the reason for the error. It simply prints "ERROR:: Exit from: src/core/pack/task/ResfileReader.cc line: 1488" - despite having a tracer output statement for the message (with endl) just before the output. |
| Steps To Reproduce | Run a protocol with a bad resfile (e.g. with a residue that doesn't exist) |
| Additional Information | I'm not sure if this is a bug in Rosetta, or it's more some issue with stream flushing on my local machine. (Note that this has been run directly in the terminal.)
I'm also not sure if it's resfile-reading specific, or a more general issue. |
| Tags | No tags attached. |
|
| Application(s) Affected | any resfile reading ones |
| Command Line Used | -resfile misnumbered.resfile |
| Developer Options | |
| Fixed in SVN Version | |
|
| Attached Files | |
|
Relationships 
Relationships