|
|
Created:
4 years, 4 months ago by hans Modified:
4 years, 4 months ago CC:
chromium-reviews, eugenis+clang_chromium.org, vmpstr+watch_chromium.org, yunlian, Reid Kleckner, glider+clang_chromium.org, Nico, ukai+watch_chromium.org, dmikurube+clang_chromium.org, inferno Base URL:
https://chromium.googlesource.com/chromium/src.git@master Target Ref:
refs/pending/heads/master Project:
chromium Visibility:
Public. |
DescriptionRoll clang 277962:278861
BUG=636558, 637866
R=dcheng@chromium.org, dpranke@chromium.org, inferno@chromium.org, rnk@chromium.org
Committed: https://chromium.googlesource.com/chromium/src/+/3829c6ad5aeef24992be742340df28c324da9e61
Patch Set 1 #Patch Set 2 : -Wno-address-of-packed-member #Patch Set 3 : try 278861 instead #Patch Set 4 : try something for ios-simulator #Patch Set 5 : Tidy up #Patch Set 6 : Widening the #ifdef #Patch Set 7 : Work around llvm.org/PR29064: compile times out compiling message_names.cc #Patch Set 8 : Build fix #
Messages
Total messages: 78 (38 generated)
hans@chromium.org changed reviewers: + rnk@chromium.org
Trying r278762 which has rnk's fix for a failing AMDGPU test.
The CQ bit was checked by hans@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: mac_chromium_rel_ng on master.tryserver.chromium.mac (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_...)
The CQ bit was checked by hans@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: mac_chromium_rel_ng on master.tryserver.chromium.mac (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_...)
try 278861 instead
Description was changed from ========== Roll clang 277962:278762. Ran `tools/clang/scripts/upload_revision.py 278762`. BUG=636558,637866 ========== to ========== Roll clang 277962:278861 BUG=636558,637866 ==========
The CQ bit was checked by hans@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: mac_chromium_rel_ng on master.tryserver.chromium.mac (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_...)
Rerunning made mac_chromium_rel_ng green, but the ios-simulator failure is persistent. We don't run ios tests on the ToT bots, so there's not much to go on :-/ I wonder if I can run this locally..
Yep, looks like we have to debug manually. The normal builder is green: https://build.chromium.org/p/chromium.mac/builders/ios-simulator/
hans@chromium.org changed reviewers: + dcheng@chromium.org
rnk figured out that the test failure is just due to the stack growing with the new clang. We already have an #ifdef for ASan, so let's expand that for this case too. rnk, I think we're good to roll dcheng: please take an OWNER's look for base/
lgtm
//base LGTM
Thanks! For those following along, I'm doing a double check on that base_unittests test just to make sure we're not growing the stack in some pathological way.
I think the increased stack size might be due to http://llvm.org/viewvc/llvm-project?rev=278356&view=rev
The CQ bit was checked by hans@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: chromium_presubmit on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)
hans@chromium.org changed reviewers: + dpranke@chromium.org
dpranke: can you take an OWNER's look at the .gn change?
inferno@chromium.org changed reviewers: + inferno@chromium.org
lgtm
The CQ bit was checked by hans@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Message was sent while issue was closed.
Description was changed from ========== Roll clang 277962:278861 BUG=636558,637866 ========== to ========== Roll clang 277962:278861 BUG=636558,637866 ==========
Message was sent while issue was closed.
Committed patchset #5 (id:80001)
Message was sent while issue was closed.
Description was changed from ========== Roll clang 277962:278861 BUG=636558,637866 ========== to ========== Roll clang 277962:278861 BUG=636558,637866 Committed: https://crrev.com/29ecb32ba7b5ca183782c5f5d2b7a1ae23309edb Cr-Commit-Position: refs/heads/master@{#412745} ==========
Message was sent while issue was closed.
Patchset 5 (id:??) landed as https://crrev.com/29ecb32ba7b5ca183782c5f5d2b7a1ae23309edb Cr-Commit-Position: refs/heads/master@{#412745}
Message was sent while issue was closed.
A revert of this CL (patchset #5 id:80001) has been created in https://codereview.chromium.org/2249163007/ by guidou@chromium.org. The reason for reverting is: This is suspect of breaking Mac 10.9 builder. See https://build.chromium.org/p/chromium.mac/builders/Mac10.9%20Tests%20%28dbg%2... Sample logs: Retrying 1 test (retry #1) [0817/224954:ERROR:kill_posix.cc(84)] Unable to terminate process group 8687: No such process [ RUN ] ThreadTest.StartWithOptions_StackSize [2060/2060] ThreadTest.StartWithOptions_StackSize (CRASHED) Retrying 1 test (retry #2) [0817/224955:ERROR:kill_posix.cc(84)] Unable to terminate process group 8688: No such process [ RUN ] ThreadTest.StartWithOptions_StackSize [2061/2061] ThreadTest.StartWithOptions_StackSize (CRASHED) Retrying 1 test (retry #3) [0817/224955:ERROR:kill_posix.cc(84)] Unable to terminate process group 8689: No such process [ RUN ] ThreadTest.StartWithOptions_StackSize [2062/2062] ThreadTest.StartWithOptions_StackSize (CRASHED) 1 test crashed: ThreadTest.StartWithOptions_StackSize (../../base/threading/thread_unittest.cc:135) Tests took 21 seconds. Additional test environment: CHROME_DEVEL_SANDBOX=/opt/chromium/chrome_sandbox LANG=en_US.UTF-8 Command: ./base_unittests --brave-new-test-launcher --test-launcher-bot-mode --test-launcher-summary-output=/b/swarm_slave/w/ionk6XHB/output.json.
Message was sent while issue was closed.
Can we just use 24K as the stack size for all platforms and cut the ifdef? We're pretty sure at this point that this stack size change was caused by a libc++ change, and affects all mac targets.
Message was sent while issue was closed.
Description was changed from ========== Roll clang 277962:278861 BUG=636558,637866 Committed: https://crrev.com/29ecb32ba7b5ca183782c5f5d2b7a1ae23309edb Cr-Commit-Position: refs/heads/master@{#412745} ========== to ========== Roll clang 277962:278861 BUG=636558,637866 ==========
On 2016/08/18 15:33:43, Reid Kleckner wrote: > Can we just use 24K as the stack size for all platforms and cut the ifdef? We're > pretty sure at this point that this stack size change was caused by a libc++ > change, and affects all mac targets. I'm widening the #ifdef to asan + non-release builds.
The CQ bit was checked by hans@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from rnk@chromium.org, dpranke@chromium.org, dcheng@chromium.org Link to the patchset: https://codereview.chromium.org/2241413003/#ps100001 (title: "Widening the #ifdef")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
lgtm x2
still lgtm
Message was sent while issue was closed.
Description was changed from ========== Roll clang 277962:278861 BUG=636558,637866 ========== to ========== Roll clang 277962:278861 BUG=636558,637866 ==========
Message was sent while issue was closed.
Committed patchset #6 (id:100001)
Message was sent while issue was closed.
Description was changed from ========== Roll clang 277962:278861 BUG=636558,637866 ========== to ========== Roll clang 277962:278861 BUG=636558,637866 Committed: https://crrev.com/df7510f96322254211068a52c2b459c0fe0b2090 Cr-Commit-Position: refs/heads/master@{#412943} ==========
Message was sent while issue was closed.
Patchset 6 (id:??) landed as https://crrev.com/df7510f96322254211068a52c2b459c0fe0b2090 Cr-Commit-Position: refs/heads/master@{#412943}
Message was sent while issue was closed.
A revert of this CL (patchset #6 id:100001) has been created in https://codereview.chromium.org/2257333002/ by hans@chromium.org. The reason for reverting is: This broke the build on a certain Mac builder: https://build.chromium.org/p/chromium/builders/Mac/builds/18669 It looks like the build is timing out maybe? All other Mac builders seem happy though, which makes this confusing, but the buildbot logs very clearly implicate the roll: the same kind of error happened last time it landed, and it went away on the previous revert..
Message was sent while issue was closed.
Description was changed from ========== Roll clang 277962:278861 BUG=636558,637866 Committed: https://crrev.com/df7510f96322254211068a52c2b459c0fe0b2090 Cr-Commit-Position: refs/heads/master@{#412943} ========== to ========== Roll clang 277962:278861 BUG=636558,637866 ==========
Third time's the charm :-) inferno: can you take an OWNER's look at the ipc_fuzzer change
lgtm
The CQ bit was checked by hans@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from rnk@chromium.org, dpranke@chromium.org, dcheng@chromium.org Link to the patchset: https://codereview.chromium.org/2241413003/#ps120001 (title: "Work around llvm.org/PR29064: compile times out compiling message_names.cc")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
More explanation for anyone looking at this: PopulateIpcMessageNames() calls ipc_fuzzer::MessageNames::Add() with a very large number of constant strings. In r278356, libc++ marked std::string::__init always_inline, which caused PopulateIpcMessageNames() to become very large and become pathologically slow to optimize. The change makes MessageNames::Add() take a "const char*" instead, which avoids constructing all the std::string objects in PopulateIpcMessageNames().
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: android_clang_dbg_recipe on master.tryserver.chromium.android (JOB_FAILED, https://build.chromium.org/p/tryserver.chromium.android/builders/android_clan...) linux_chromium_chromeos_rel_ng on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...) linux_chromium_rel_ng on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
The CQ bit was checked by hans@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from rnk@chromium.org, dpranke@chromium.org, dcheng@chromium.org, inferno@chromium.org Link to the patchset: https://codereview.chromium.org/2241413003/#ps140001 (title: "Build fix")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
lgtm
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: linux_android_rel_ng on master.tryserver.chromium.android (JOB_FAILED, https://build.chromium.org/p/tryserver.chromium.android/builders/linux_androi...)
The CQ bit was checked by inferno@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: linux_android_rel_ng on master.tryserver.chromium.android (JOB_FAILED, https://build.chromium.org/p/tryserver.chromium.android/builders/linux_androi...)
On 2016/08/20 06:34:13, commit-bot: I haz the power wrote: > Try jobs failed on following builders: > linux_android_rel_ng on master.tryserver.chromium.android (JOB_FAILED, > https://build.chromium.org/p/tryserver.chromium.android/builders/linux_androi...) That test seems to be failing a lot on that bot, for other changes than this. Given that the roll has been landed twice before without any problems with unit_tests on Android, I'll land manually.
(The bad trybot is http://crbug.com/639538)
Message was sent while issue was closed.
Description was changed from ========== Roll clang 277962:278861 BUG=636558,637866 ========== to ========== Roll clang 277962:278861 BUG=636558,637866 R=dcheng@chromium.org, dpranke@chromium.org, inferno@chromium.org, rnk@chromium.org Committed: https://crrev.com/3829c6ad5aeef24992be742340df28c324da9e61 Cr-Commit-Position: refs/heads/master@{#413337} ==========
Message was sent while issue was closed.
Patchset 8 (id:??) landed as https://crrev.com/3829c6ad5aeef24992be742340df28c324da9e61 Cr-Commit-Position: refs/heads/master@{#413337}
Message was sent while issue was closed.
Description was changed from ========== Roll clang 277962:278861 BUG=636558,637866 R=dcheng@chromium.org, dpranke@chromium.org, inferno@chromium.org, rnk@chromium.org Committed: https://crrev.com/3829c6ad5aeef24992be742340df28c324da9e61 Cr-Commit-Position: refs/heads/master@{#413337} ========== to ========== Roll clang 277962:278861 BUG=636558,637866 R=dcheng@chromium.org, dpranke@chromium.org, inferno@chromium.org, rnk@chromium.org Committed: https://chromium.googlesource.com/chromium/src/+/3829c6ad5aeef24992be742340df... ==========
Message was sent while issue was closed.
Committed patchset #8 (id:140001) manually as 3829c6ad5aeef24992be742340df28c324da9e61 (presubmit successful). |