Open Bug 1496285 Opened 7 years ago Updated 3 years ago

Fix differences between JSDCOV and JSVM in coverage of XML files

Categories

(Testing :: Code Coverage, defect, P3)

Version 3
defect

Tracking

(Not tracked)

People

(Reporter: sparky, Unassigned)

References

(Depends on 1 open bug, Blocks 1 open bug)

Details

Attachments

(1 file)

Attached file differences.txt
Looking at the raw data from these two pushes: JSDCOV: https://treeherder.mozilla.org/#/jobs?repo=try&selectedJob=201089393&revision=f90b8cdb2cefb9e39f37db54415645df0055ae69 JSVM: https://treeherder.mozilla.org/#/jobs?repo=try&selectedJob=201089393&revision=22abb99d81005498bf86ec6cd896fb1c5e6c8fcf I've attached the coverage for the XML files as an attachment. This bug is to look into the differences, and file bugs to ensure JSVM has the same coverage of XML files as JSDCOV coverage.
Links were backwards: > JSVM: > https://treeherder.mozilla.org/#/ > jobs?repo=try&selectedJob=201089393&revision=f90b8cdb2cefb9e39f37db54415645df > 0055ae69 > > JSDCOV: > https://treeherder.mozilla.org/#/ > jobs?repo=try&selectedJob=201089393&revision=22abb99d81005498bf86ec6cd896fb1c > 5e6c8fcf
Depends on: 1496286
Depends on: 1496292

I wonder if we can still run JSDCOV to check again if there is some coverage in JSDCOV which is not in JSVM.

Priority: -- → P3
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: