On 2015/06/03 17:02:50, rmcilroy wrote:
On 2015/06/03 16:50:41, mtbrandyberry wrote:
> On 2015/06/03 15:54:32, rmcilroy wrote:
> > On 2015/06/03 15:44:26, mtbrandyberry wrote:
> > > On 2015/06/03 03:02:50, commit-bot: I haz the power wrote:
> > > > Patchset 1 (id:??) landed as
> > > > https://crrev.com/51439db3b287faed806e9a1cae33bc3498feeaf6
> > > > Cr-Commit-Position: refs/heads/master@{#28772}
> > >
> > > It's not obvious how this change could have broken this since it
should
be
> > > mostly a no-op for ia32. Are there build artifacts available that
I can
use
> > to
> > > reproduce the problem and debug?
> >
> > You can see the build logs here:
> >
>
http://build.chromium.org/p/client.v8/builders/V8%20Linux%20-%20nosnap%20-%20debug%20-%202/builds/609/
> >
> > You can recreate the build locally by building with something like:
> >
> > make ia32.debug snapshot=off
>
> I'm not able to reproduce this:
>
> $ git log --pretty=oneline -n1
> a9404029343d65f146e3443f5280c40a97e736af Add support for Embedded
Constant
Pools
> for PPC and Arm
>
> $ make ia32.debug snapshot=off
> <...>
>
> $ out/ia32.debug/cctest --random-seed=-2035604219 --stress-opt
--always-opt
> test-api/FastReturnValuesWithProfiler --nohard-abort
--nodead-code-elimination
> --nofold-constants --enable-slow-asserts --debug-code --verify-heap
>
--testing_serialization_file=out/.serdes/serdes_FastReturnValuesWithProfiler__stress_opt__always_opt
> $
Benedikt: This only happened once on the bot from what I can see. Are you
sure
it wasn't just flake?
I've been running this in a loop on various machines all afternoon without
reproducing. I've tried the commit referenced above, the one immediately
after
(where the bot reported it), and the latest code with the constant pool
change
re-applied. No failures.
https://codereview.chromium.org/1155703006/
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
