Report during review phase build errors for files that have been fixed to be compatible to the non-unified system
Categories
(Developer Infrastructure :: Source Code Analysis, enhancement)
Tracking
(firefox83 fixed)
| Tracking | Status | |
|---|---|---|
| firefox83 | --- | fixed |
People
(Reporter: andi, Assigned: andi)
Details
Attachments
(1 file)
Since we've started fixing modules for mozilla-central in order to have the compile outside of the unified environment we should have a mechanism in place that reports errors when patches break them.
| Assignee | ||
Updated•6 years ago
|
| Assignee | ||
Updated•6 years ago
|
| Assignee | ||
Comment 1•6 years ago
|
||
-
We build a list with directories, from
non-unified-compatthat have been fixed and
permit compiling of C++ files outside of the unified environment. With this list
we eliminate the unified sources and instead use the original source forcommand
attribute fromcompile_commands.json.
In this way if a regression appearsclang-tidywill report it since it no longer uses
the unified environment for files that are compatible to be compiled standalone. -
Remove the coverity functionality that was reading and using non-unified build files
since in practive it prooved to be sub-optimal.
Updated•6 years ago
|
Comment 3•6 years ago
|
||
| bugherder | ||
Updated•4 years ago
|
Description
•