Open Bug 1524116 Opened 5 years ago Updated 2 years ago

Documentation on running code coverage on try and building locally is out of date

Categories

(Testing :: Code Coverage, defect, P2)

Version 3
defect

Tracking

(Not tracked)

People

(Reporter: ng, Unassigned)

References

Details

The documentation on MDN on running code coverage builds is out of date: https://developer.mozilla.org/en-US/docs/Mozilla/Testing/Measuring_Code_Coverage_on_Firefox

I am attempting to reproduce a bug that only appears on linux64 code coverage builds, and the steps outlined on MDN don't appear to work. The cargo linker fails with /usr/lib/llvm-7/lib/clang/7.0.0/lib/linux/libclang_rt.profile-x86_64.a(GCDAProfiling.c.o):function llvm_gcov_init: error: undefined reference to 'atexit'.

There don't appear to be any *-ccov tasks available in the fuzzy try chooser.

Coincidentally, I was thinking about updating the docs a few hours ago... Hopefully we'll do it soon.

Regarding scheduling on try, you can do it by passing --full to mach try fuzzy. There are several ccov builds, you probably want linux64-ccov/debug.

Marco, thanks, --full was indeed what I needed for try.

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