Bug #7953
closed
Problem with mark creation
Added by Anton Vasilyev about 7 years ago.
Updated about 7 years ago.
Description
http://ldvstore:8998/reports/unsafe/136228/
On mark creation with
Description: of configfs_fs_type->s_op->put_super, where s_op==NULL."
Tags: EMG->EnvSpec
Error traces conversion function: call_forests
Error traces comparison function: call_forests_compare
Verdict: Unknown
Status: Unreported
Bridge reply with error: "list index out of range"
- Assignee changed from Evgeny Novikov to Vladimir Gratinskiy
- Priority changed from Normal to Immediate
The error trace visualization also doesn't look good.
- Due date set to 02/06/2017
- Status changed from New to Resolved
- % Done changed from 0 to 100
Fixed in fix_7953. But as you see in this error trace, warning is not for any function enter and there are no function enters in call stack from enter callback action to warning, so warning doesn't affect converted error trace in convert functions with forests algorithms.
- Status changed from Resolved to Open
Although it is a bit unrelated issue, but I worry why there is not detailed information on such the problems in Bridge logs - just "list index out of range" in UI. In other places there is "Unknown error" (or something more appropriate) + detailed information in logs.
As for limitations of the default converting/comparison algorithms, this is good to know but it shouldn't hurt anybody since they are just they are.
- Status changed from Open to Closed
I merged the branch to master in 9072a9d. Let's consider another issue separately.
Also available in: Atom
PDF