Displaying #cassandra-dev/2017-01-30.log:

Mon Jan 30 00:18:24 2017  mstepura:Joined the channel
Mon Jan 30 01:13:54 2017  kohlisankalp:Joined the channel
Mon Jan 30 01:34:40 2017  clohfink:Joined the channel
Mon Jan 30 03:22:49 2017  clohfink:Joined the channel
Mon Jan 30 03:30:09 2017  Vijay__:Joined the channel
Mon Jan 30 03:32:02 2017  clohfink:Joined the channel
Mon Jan 30 04:29:19 2017  ossarga:Joined the channel
Mon Jan 30 06:01:26 2017  kvaster:Joined the channel
Mon Jan 30 07:35:14 2017  visheshnp:Joined the channel
Mon Jan 30 07:53:02 2017  spodkowinski:Joined the channel
Mon Jan 30 09:01:32 2017  cosql:Joined the channel
Mon Jan 30 09:02:52 2017  cosql:Joined the channel
Mon Jan 30 09:03:47 2017  cosql:Joined the channel
Mon Jan 30 11:54:52 2017  ossarga:Joined the channel
Mon Jan 30 13:01:27 2017  RussSpitzer:Joined the channel
Mon Jan 30 13:48:08 2017  charliek:Joined the channel
Mon Jan 30 13:55:35 2017  ossarga:Joined the channel
Mon Jan 30 14:25:12 2017  adamholmberg:Joined the channel
Mon Jan 30 14:54:00 2017  jfarrell_:Joined the channel
Mon Jan 30 14:57:07 2017  ossarga:Joined the channel
Mon Jan 30 15:15:43 2017  dbourlat:Joined the channel
Mon Jan 30 15:20:58 2017  dbourlat:I'm running unit tests on trunk (Jan 25, 2987a7093c) - everything is fine except timeouts in these test suites: ViewFilteringTest, ViewTest, SecondaryIndexTest, AggregationTest, SelectTest. Is this a known / expected issue? Thx.
Mon Jan 30 15:26:00 2017  exlt:you can compare to here - https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-trunk-test/lastCompletedBuild/testReport/
Mon Jan 30 15:27:58 2017  exlt:not sure what kind of hardware your tests are running on, but I'd suspect a small or busy system could trigger timeouts
Mon Jan 30 15:30:00 2017  exlt:we tend to run tests on 16G RAM with nothing else running - m3.xlarge AWS instance type is about right
Mon Jan 30 15:30:49 2017  exlt:SSD for sure - busy spinning disk i/o could trigger timeouts
Mon Jan 30 15:31:33 2017  dbourlat:not SSD in this case - just a basic spindle, not high-end
Mon Jan 30 15:31:56 2017  dbourlat:I'll set up a memdisk then and re-try :)
Mon Jan 30 15:34:38 2017  exlt:if you're hitting junit timeouts and not actual test timeouts, you might also try just bumping up the timeout: `ant test -Dtest.timeout=600000` (default on main test target is 240000)
Mon Jan 30 15:35:41 2017  dbourlat:I see. Thanks for the tip.
Mon Jan 30 15:36:09 2017  dbourlat:This system is not busy. It's my dev box, but I guess the disk might be too slow for these tests
Mon Jan 30 15:37:09 2017  exlt:it's a likely candidate - been there ;)
Mon Jan 30 15:43:11 2017  dbourlat:trying SSD now...
Mon Jan 30 17:02:21 2017  maedhroz:Joined the channel
Mon Jan 30 17:13:45 2017  mstepura:Joined the channel
Mon Jan 30 17:16:08 2017  Vijay_:Joined the channel
Mon Jan 30 17:32:57 2017  kohlisankalp:Joined the channel
Mon Jan 30 17:53:38 2017  JayZhuang:Joined the channel
Mon Jan 30 18:27:15 2017  kvaster:Joined the channel
Mon Jan 30 18:29:01 2017  JayZhuang1:Joined the channel
Mon Jan 30 18:34:52 2017  kohlisankalp:Joined the channel
Mon Jan 30 18:36:44 2017  clohfink:Joined the channel
Mon Jan 30 18:37:29 2017  clohfink:Joined the channel
Mon Jan 30 18:41:53 2017  kohlisankalp:Joined the channel
Mon Jan 30 18:42:59 2017  Vijay_:Joined the channel
Mon Jan 30 18:53:09 2017  JayZhuang:Joined the channel
Mon Jan 30 18:58:33 2017  ossarga:Joined the channel
Mon Jan 30 19:03:19 2017  cosql:Joined the channel
Mon Jan 30 19:03:38 2017  JayZhuang:Joined the channel
Mon Jan 30 19:12:04 2017  jmckenzie_:Joined the channel
Mon Jan 30 19:30:03 2017  Vijay_:Joined the channel
Mon Jan 30 19:52:29 2017  JayZhuang:Joined the channel
Mon Jan 30 19:52:38 2017  clohfink:Joined the channel
Mon Jan 30 20:03:07 2017  nickmbailey:Joined the channel
Mon Jan 30 20:19:42 2017  mstepura:Joined the channel
Mon Jan 30 20:41:12 2017  ossarga:Joined the channel
Mon Jan 30 21:22:18 2017  dbourlat:Joined the channel
Mon Jan 30 21:27:26 2017  dbourlat:by the way, running tests on SSD did help :)
Mon Jan 30 21:28:13 2017  dbourlat:another question about CQL grammar: I'm adding another statement with "MAX" as a keyword. Apparently it clashes with "max" used as a function name in some case
Mon Jan 30 21:28:24 2017  dbourlat:any tips on resolving this?
Mon Jan 30 21:29:01 2017  dbourlat:so far I ended up using semantic predicates and treat MAX as an IDENT but hope there may be a nicer solution :) Thx.
Mon Jan 30 21:29:38 2017  dbourlat:by keyword I meant a lexer token (above)
Mon Jan 30 21:49:57 2017  kohlisankalp:Joined the channel
Mon Jan 30 22:09:45 2017  adamholmberg:Joined the channel
Mon Jan 30 22:11:04 2017  kohlisankalp:Joined the channel
Mon Jan 30 22:28:53 2017  kohlisankalp:Joined the channel
Mon Jan 30 23:30:24 2017  Vijay_:Joined the channel
Mon Jan 30 23:34:00 2017  nickmbailey:Joined the channel
Mon Jan 30 23:43:18 2017  Vijay_:Joined the channel

Comments