[meta] replace manifestparser .ini with .toml
Categories
(Testing :: General, task)
Tracking
(Not tracked)
People
(Reporter: jmaher, Unassigned)
References
(Depends on 7 open bugs, Blocks 1 open bug, Regressed 1 open bug)
Details
(Keywords: meta)
this is the master bug, a project is outlined here:
https://docs.google.com/document/d/1VV_1ao4f1mnR7n1fRqz_KbX7ybUBFieszPCShbwFWVo/edit
Comment 1•2 years ago
|
||
I've just filed bug 1847580 which will need fixing as part of this - currently ESLint reads the test manifest .ini
files to work out various details, and so that will need updating to read toml files before they ini files are made redundant/removed.
Comment 2•2 years ago
|
||
A couple more thoughts:
I'd assume that ./mach addtest
will also need fixing. Though I'm not quite sure where this should be filed.
Should we add a .toml
handling extension to the recommended list for VS Code (see .vscode/extensions.json
)? I would assume it would give us syntax highlighting and that might make it easier to read and edit.
Updated•1 years ago
|
Reporter | ||
Updated•1 years ago
|
Comment 3•1 year ago
|
||
I think each of these changes is making manifest parsing slower, and is the cause for the slow drift in time spent in configure: https://treeherder.mozilla.org/perfherder/graphs?highlightAlerts=1&highlightChangelogData=1&highlightCommonAlerts=0&series=autoland,4200695,1,2&timerange=5184000
Before this all started, we had:
Finished reading 2285 moz.build files in 4.72s
Now, we have:
Finished reading 2288 moz.build files in 23.25s
And a local python profile shows most of the time spent in read_toml.
Comment 4•1 year ago
|
||
I'll also note that bug 1779473 added tomlkit, while we already had toml, and that crudely replacing tomlkit with toml in testing/mozbase/manifestparser/manifestparser/toml.py brings down the time spent in read_toml substantially.
Comment 5•1 year ago
|
||
The choice of tomlkit
over toml
was intentional due to the former library's ability to edit TOML files while preserving comments (to be used in future automation).
We can use Bug 1859997 to track read_toml
performance
Comment 6•1 month ago
|
||
Are conversions by hand, or do you have something scripted to help?
Reporter | ||
Comment 7•1 month ago
|
||
they were scripted, in general you can read/write from manifestparser, so try using that for reading the .ini and then writing out a .toml.
Description
•