[fuchsia][blink] Remove unnecessary merger and clean up logic The files have never been written into the output folder because the `--logs-dir` has never been set. See the following examples. https://chromium-swarm.appspot.com/task?id=6aad8ab6718f6c10 https://chromium-swarm.appspot.com/task?id=6aad8ab68af87310 Cq-Include-Trybots: luci.chromium.try:fuchsia-fyi-arm64-dbg,fuchsia-x64-cast-receiver-dbg,fuchsia-x64-cast-receiver-rel,fuchsia-arm64-cast-receiver-rel;luci.chrome.try:fuchsia-smoke-sherlock,fuchsia-smoke-nelson,fuchsia-smoke-astro Change-Id: Ibeffae2b522335a2999831f6d344c20b2c07018e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5685319 Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org> Commit-Queue: Zijie He <zijiehe@google.com> Cr-Commit-Position: refs/heads/main@{#1325007}
ChromiumChromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.