Generate target.json for spidermonkey shell builds
Categories
(Core :: JavaScript Engine, enhancement, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox73 | --- | fixed |
People
(Reporter: sfink, Assigned: sfink)
Details
Attachments
(1 file)
@jason is looking into adding spidermonkey jobs into a fuzzing test harness of some sort, but is downloading from a "latest" URL and uses target.json to identify the version of the build being grabbed.
For browser builds, it looks like target.json is generated during the packaging step, which does not exist for the shell builds. (Even if you build the JS shell with mach and --enable-project=js, mach package does not work.)
|
Assignee | |
Comment 1•4 years ago
|
||
The browser build generates this file during the packaging step, which does not exist for JS shell builds. I made a brief attempt to call informulate.py as it does, but that seemed to require some things that are not available during the shell build. So I went with the cheap and easy approach to provide just the fields :jkratzer uses.
|
||
Updated•4 years ago
|
Pushed by sfink@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/96e66af66715 Write out a minimal target.json file for spidermonkey shell builds. r=froydnj
|
||
Comment 3•4 years ago
|
||
| bugherder | ||
Description
•