Closed Bug 1364940 Opened 5 years ago Closed 4 years ago

JSVM code coverage generates SF records that span multiple lines

Categories

(Core :: JavaScript Engine, defect)

defect
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: marco, Unassigned)

References

(Blocks 1 open bug)

Details

For example:

TN:moz_2dnullprincipal_3a_7b698a1e07_2dfa3f_2d4182_2d85a9_2d5e2d3b31a59d_7d_2c_20XPConnect_20Compilation_20Compartment
SF:data:,new function() {
      Components.utils.import("resource://gre/modules/RemoteAddonsChild.jsm");
    }
FN:1,top-level
FN:1,top-level
FNF:2
FNH:0
BRF:0
BRH:0
LF:0
LH:0
end_of_record
What is the importance of this bug?

Last time I heard about using the lcov output produced by the JS engine, this was not a priority because our tooling were using the JS Debugger API to produce the output as a per test basis.
Flags: needinfo?(mcastelluccio)
I think we are going to enable the JSVM code coverage first, as the JS Debugger API has some limitations. Joel can give more details.
Flags: needinfo?(mcastelluccio) → needinfo?(jmaher)
we are planning to use JSVM coverage for everything- so we will be looking to fix this bug and other bugs in the near future.  js debugger api is great, but solves a different problem.
Flags: needinfo?(jmaher)
I guess we can close this as with the rewriter (bug 1224691) we're just ignoring these entries.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.