InitSDK stage seems slow |
|||
Issue descriptionSimilar to https://bugs.chromium.org/p/chromium/issues/detail?id=620544 InitSDK stage also seems like it's getting slow. Example: https://uberchromegw.corp.google.com/i/chromeos/builders/daisy_skate-paladin/builds/6915/steps/InitSDK/logs/stdio Part of that I think is because it is needing to build some new CLs that affect the sdk (like ghostscript?). Not sure if these really need to be in the sdk though.
,
Jun 17 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/5e5da7a58e847b0233d8b03e08f3dd740b05bc36 commit 5e5da7a58e847b0233d8b03e08f3dd740b05bc36 Author: Brian Norris <briannorris@chromium.org> Date: Thu Jun 16 02:34:55 2016 sdk: don't pull in ghostscript We're pulling CUPS into the SDK (b/c icedtea is silly...). But that doesn't mean we need to pull in Ghostscript too; plus, Ghostscript currently builds really slow, since it isn't using parallel make at the moment. Use the new USE=postscript flag to disable ghostscript-based filters and remove the dependency. BUG= chromium:620545 TEST=trybots Change-Id: Iae54dc4b786877f175cf1a806fb496d206d2cb33 Signed-off-by: Brian Norris <briannorris@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/353190 Reviewed-by: Aviv Keshet <akeshet@chromium.org> [modify] https://crrev.com/5e5da7a58e847b0233d8b03e08f3dd740b05bc36/profiles/targets/sdk/package.use
,
Jun 17 2016
I verified we're no longer pulling in ghostscript for the SDK, and that the emerge was taking around 8 to 10 minutes sometimes (yikes!). Should be fixed. Feel free to reopen and/or reassign if there are other slowness issues to investigate.
,
Jun 27 2016
Closing... please feel free to reopen if its not fixed.
,
Jun 27 2016
|
|||
►
Sign in to add a comment |
|||
Comment 1 by briannorris@chromium.org
, Jun 16 2016Status: Started (was: Untriaged)