00:17:22  <aklein>jwolfe: neat. now you should do that python hacking inside run-tests.py and add a new flag :)
00:19:39  <jwolfe>aklein, sounds fun. how do i open an issue for that? i assume i use this form and let other people worry about what "component" it's for and stuff: https://bugs.chromium.org/p/v8/issues/entry
00:20:26  <jwolfe>and then i follow the normal CL process like for the rest of v8
00:21:06  <aklein>jwolfe: for something as small as this you don't even need a monorail issue if you don't want to. otherwise I'd say the "Infrastructure" component is what you'd want
00:21:34  <jwolfe>where do i discuss how it should work? right here?
00:22:03  <aklein>naw, if there are options then a bug seems like a good place
00:22:23  <aklein>and yeah, it goes under the v8 project just like anything else
00:22:35  <jwolfe>k
00:23:58  * unixpicklequit (Quit: Peace out)
00:35:46  * unixpicklejoined
00:47:14  * unixpicklequit (Quit: My Mac has gone to sleep. ZZZzzz…)
00:48:02  <jwolfe>aklein: https://bugs.chromium.org/p/v8/issues/detail?id=5208
01:34:31  * srl295quit (Quit: No Ping reply in 180 seconds.)
01:36:19  * srl295joined
01:36:19  * srl295quit (Changing host)
01:36:19  * srl295joined
01:51:03  * unixpicklejoined
01:51:23  * unixpicklequit (Client Quit)
03:24:41  * Garbeequit (Quit: Connection closed for inactivity)
09:18:37  * stalledquit (Ping timeout: 260 seconds)
09:23:57  * plutoniixquit (Ping timeout: 276 seconds)
09:36:06  * plutoniixjoined
09:50:21  * zvquit (Ping timeout: 244 seconds)
10:06:45  * zvjoined
10:07:59  * stalledjoined
11:14:52  * Garbeejoined
12:09:14  <trungl-bot>Tree closed by buildbot@chromium.org: Tree is closed (Automatic: "SimdJs - all" on http://build.chromium.org/p/client.v8/builders/V8%20Win64%20-%20debug/builds/11115 "V8 Win64 - debug" from 460e0b80a919c8f2dbc17c9742732ca0c18a54e4: jochen@chromium.org (:jochen__),nikolaos@chromium.org)
12:13:14  <jochen__>my change just renamed a method
12:22:21  <trungl-bot>Tree opened by buildbot@chromium.org: Tree is open (Automatic: Zorte on!)
12:43:30  <trungl-bot>Tree closed by buildbot@chromium.org: Tree is closed (Automatic: "Fuzz on Ubuntu-12.04" on http://build.chromium.org/p/client.v8/builders/V8%20Fuzzer/builds/11248 "V8 Fuzzer" from 562bb5823c4dd4eb8520b0f3fd3a969d3c4922cd: jochen@chromium.org (:jochen__))
13:00:39  <trungl-bot>Tree opened by buildbot@chromium.org: Tree is open (Automatic: 祝你好運!)
13:04:03  <jochen__>whatever
13:04:59  * davijoined
13:19:50  * daviquit (Ping timeout: 272 seconds)
14:30:55  * stalledquit (Max SendQ exceeded)
14:46:31  * stalledjoined
15:21:32  * davijoined
15:21:32  * daviquit (Changing host)
15:21:32  * davijoined
15:46:05  * RT|Chatzillaquit (Quit: ChatZilla 0.9.86.1 [Firefox 2.0.0.22pre/2010030309])
15:46:46  * seventhjoined
15:51:12  * stalledquit (Ping timeout: 272 seconds)
16:04:14  * akleinquit (Ping timeout: 250 seconds)
16:04:34  * akleinjoined
16:12:28  * daviquit (Ping timeout: 250 seconds)
16:22:01  * stalledjoined
17:22:03  * lerelapart ("Leaving")
18:56:11  * zvquit (Read error: Connection timed out)
19:02:22  * fairfieldtjoined
19:19:36  * zvjoined
20:21:02  * davijoined
20:33:28  * daviquit (Ping timeout: 264 seconds)
20:34:58  * seventhquit (Quit: ...)
22:06:37  <jwolfe>is it ok to put non-ascii unicode characters (like ♔) directly in an mjsunit test? it's going in a string literal, so I could also use \u2654 if that would be better.
22:23:30  <jwolfe>i think for my case, i should use \u2654 regardless of the answer to the above question. so never mind i guess.
22:30:47  * RT|Chatzillajoined
22:45:12  <aklein>jwolfe: I'd vote for the escaped literal, but it sounds like you already landed on that
22:45:54  <jwolfe>aklein, thanks for the general info. i'll keep it in mind.
22:52:57  <aklein>jwolfe: no particular reason for my choice, other than less chance of some tool failing to reproduce it correctly
22:58:10  <aklein>jwolfe: did you see jkummerow's response re: allow_* flags? https://groups.google.com/d/msg/v8-dev/QQ56GC-jniI/b1SnClwxBgAJ
23:13:55  <jwolfe>aklein, no i didn't. thanks.
23:14:21  <jwolfe>so i guess i need to learn how cctest presumably configures the flags at runtime while multiple threads are running and reading those flags.
23:14:33  <jwolfe>that's seems like a recipe for disaster