This patch changes the table pointers (which are mostly null) into uint8_t
offsets into a much smaller table of strings.
This shrinks the four arrays by a combined total of 3 KiB, and also makes them
shareable between processes.
--HG--
extra : rebase_source : 96874aa9eb32f48011ac6ae6de8a930c57112263
The css_properties.js rule can be converted into gen-css-properties.py,
which we can install with TEST_HARNESS_FILES instead of the
mochitest.ini manifest.
MozReview-Commit-ID: F7nf71ORWsS
If we add an ObjDirPath as an input to a GENERATED_FILES script, we
should run it in the misc tier to ensure the dependent files are created
beforehand. We need to use Path objects instead of raw filenames in the
GeneratedFile object so the recursive make backend can distinguish
between source and objdir files.
MozReview-Commit-ID: 9thHTi75zdI
By using a timer the first invocation of the callback is happening after the specified interval.
That means by a default of 100ms we loose that time on every call of implicit wait, and it will
slow-down the test execution drastically. To prevent this lets manually invoke the callback
before starting the timer.
MozReview-Commit-ID: Ayy1GPEaY92
--HG--
extra : rebase_source : 2fac7b5578ec42af5050fad21ca9c3d5cfdca3e1
When the application is asked to quit, all windows are checked to see if
they can close (which will spawn the permit unload dialogs). Once the
user grants the quit via the permit unload dialogs, nsIAppStartup
returns true for the shuttingDown attribute, and we know that all
windows allowed the shutdown to occur. This means that we don't
have to show the permitUnload dialogs again when SessionStore
attempts to close the windows when it does its final async window
flush during the quit-application-granted observer topic.
MozReview-Commit-ID: DOy8ljngnTd
--HG--
extra : rebase_source : 585a75959fb8f441349594d2c3569f1de984eb44
As part of unblocking building with VS2015u1 in automation, I'm mass
disabling compiler warnings that are turned into errors. This is not
the preferred mechanism to fix compilation warnings. So hopefully
someone fixes the underlying problem someday. However, there are tons
of ignored warnings in security/certverifier, so I guess the workaround
in this patch is par for the course.
MozReview-Commit-ID: 7GZ9RpkxnwT
--HG--
extra : rebase_source : 023a438b6458fb4859018cde421d51072f0f0490
As part of unblocking building with VS2015u1 in automation, I'm mass
disabling compiler warnings that are turned into errors. This is not
the preferred mechanism to fix compilation warnings. But the warning
occurs in third party code, so my hands are tied.
MozReview-Commit-ID: BCXQcEejre9
--HG--
extra : rebase_source : a36a432edc834ec806dd4341f247143b178902a4
As part of unblocking building with VS2015u1 in automation, I'm mass
disabling compiler warnings that are turned into errors. This is not
the preferred mechanism to fix compilation warnings. So hopefully
this patch never lands because someone insists of fixing the underlying
problem instead. But if it does land, hopefully the workaround is
only temporary.
MozReview-Commit-ID: 9AkkAUDMln6
--HG--
extra : rebase_source : 76126361de678729344b0e9eaeac1d523f88ebb4
As part of unblocking building with VS2015u1 in automation, I'm mass
disabling compiler warnings that are turned into errors. This is not
the preferred mechanism to fix compilation warnings. But the warning
occurs in third party code, so my hands are tied.
MozReview-Commit-ID: 6n8nl517Ly
--HG--
extra : rebase_source : 19c1c012e1ddf15accbdf1a1050e4d607f9c7b31
