Opened 11 years ago
Last modified 11 years ago
#463 reopened misbehavior
catch more errors from GDE methods
Reported by: | westram | Owned by: | westram |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Usability | Version: | SVN |
Keywords: | Cc: |
Description (last modified by westram)
Change History (5)
comment:1 Changed 11 years ago by westram
- Owner changed from devel to westram
- Status changed from new to assigned
comment:2 Changed 11 years ago by westram
- Description modified (diff)
comment:3 Changed 11 years ago by westram
- Description modified (diff)
comment:4 in reply to: ↑ description ; follow-up: ↓ 5 Changed 11 years ago by westram
- Resolution set to fixed
- Status changed from assigned to closed
comment:5 in reply to: ↑ 4 Changed 11 years ago by westram
- Resolution fixed deleted
- Status changed from closed to reopened
Replying to westram:
- extract from logs (e.g. RAxML)
No way - if an error occurs in RAxML, it prints it to console, but doesn't print it into the log.
Really need some solution for that (see also mgg ticket 278).
Maybe redirect output, pass through 'tee' and parse it in case of RAxML errors?
Note: See
TracTickets for help on using
tickets.
No way - if an error occurs in RAxML, it prints it to console, but doesn't print it into the log.