Closed
Description
Summary
When running flow latency analysis there are cases where no report is created and no error is logged.
Expected and Current Behavior
An analysis report should be created or an error log entry should appear. Currently an NPE is thrown that is only printed to the console.
Steps to Reproduce
- Instantiate issue2423::top.i
- Run flow latency analysis
- Observe NPE logged to console
package issue2423
public
abstract E
features
odp: out data port;
flows
src: flow source odp;
end E;
abstract implementation E.i
end E.i;
abstract C
features
cfg: feature group FG;
flows
snk: flow sink cfg.idp {
Latency => 1ms .. 1ms;
};
end C;
feature group FG
features
idp: in data port;
end FG;
system top
end top;
system implementation top.i
subcomponents
e: abstract E;
c: abstract C;
connections
c1: feature e.odp -> c.cfg.idp;
flows
ete: end to end flow e.src -> c1 -> c.snk;
end top.i;
end issue2423;
Environment
- OSATE Version: 2.8.0
- Operating System: WIndows