Signed Linux builds are ~10M in size
Categories
(Testing :: geckodriver, defect)
Tracking
(Not tracked)
People
(Reporter: ato, Unassigned)
Details
I noticed after uploading the geckodriver 0.26.0 release that the Linux binaries for both 32- and 64-bit are around ~10M in size, whereas the macOS and Windows (32-bit) builds are around ~1.3M in size.
https://github.com/mozilla/geckodriver/releases/tag/v0.26.0
This should be investigated.
|
Reporter | |
Comment 1•6 years ago
|
||
Can you shine some light on why the signed builds are so big?
|
||
Comment 2•6 years ago
|
||
Again, we don't want to use the signed builds on Linux! That's not what we did for the last release. Instead we really have to use the builds from the toolchain jobs! See also bug 1442253 which this is a dupe of.
|
|
Reporter | |
Comment 3•6 years ago
|
||
-
It’s confusing to pick release builds from different TaskCluster jobs. Can you explain why we don’t want to use the Linux builds from the same job?
-
If this is a duplicate, why is bug 1442253 when the binaries produced on the
Gd(s)job are too big? Should one of them be re-opened?
|
|
||
Comment 4•6 years ago
|
||
We already discussed this a couple of times. So once again, the fix to strip all the debug info only landed for the toolchain builds which is/was our target for future release builds. But problems with the notarization on MacOS could change that.
Description
•