obj/static-analysis/compile_commands.json is sometimes not updated
Categories
(Developer Infrastructure :: Source Code Analysis, defect, P2)
Tracking
(firefox-esr91 unaffected, firefox99 wontfix, firefox100 wontfix, firefox101 fix-optional)
Tracking | Status | |
---|---|---|
firefox-esr91 | --- | unaffected |
firefox99 | --- | wontfix |
firefox100 | --- | wontfix |
firefox101 | --- | fix-optional |
People
(Reporter: saschanaz, Unassigned)
References
(Regression)
Details
(Keywords: regression)
I had to remove and rerun static-analysis check
to refresh the file and get dom/streams
included (which is behind a build flag and is recently enabled by default, bug 1752206).
Reporter | ||
Updated•2 years ago
|
Comment 1•2 years ago
|
||
What do you mean? Could you please details more your issue and the environment where it occur?
Reporter | ||
Comment 2•2 years ago
•
|
||
- Get a mozconfig with
--disable-dom-streams
./mach build && ./mach static-analysis check dom/abort
- Remove
--disable-dom-streams
from the config ./mach build && ./mach static-analysis check dom/streams
- Check
obj/static-analysis/compile_commands.json
Last time I tried this, the file didn't include any file in dom/streams
.
Edit: Actually it wasn't the config that was edited, it was the moz.configure. Not sure that can cause any difference here, though.
Comment 3•2 years ago
|
||
The severity field is not set for this bug.
:andi, could you have a look please?
For more information, please visit auto_nag documentation.
Updated•2 years ago
|
Comment 5•2 years ago
|
||
:mgaudet, since you are the author of the regressor, bug 1752206, could you take a look?
For more information, please visit auto_nag documentation.
Updated•2 years ago
|
Updated•2 years ago
|
Reporter | ||
Comment 6•2 years ago
|
||
Not sure how bug 1756025 can cause this? I'd rather say it discovered the issue...
Comment 7•2 years ago
|
||
It was a copy and paste error, I wanted to paste bug 1752206.
Updated•2 years ago
|
Reporter | ||
Comment 8•2 years ago
|
||
Oh sorry, I was to say bug 1752206. That just enabled a flag, and doing so shouldn't cause this kind of issue.
Updated•2 years ago
|
Comment 9•2 years ago
|
||
Set release status flags based on info from the regressing bug 1752206
Updated•2 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Description
•