testing - Figuring out which test case failed in Elasticsearch source -


after forking , downloading elasticsearch, tried running tests gradle check. execution took 2 hours , shown in stack blow there 1 error.

   [junit4]     @ com.carrotsearch.ant.tasks.junit4.dependencies.com.google.common.eventbus.eventbus.post(eventbus.java:215)    [junit4]     @ com.carrotsearch.ant.tasks.junit4.localslavestreamhandler.pumpevents(localslavestreamhandler.java:260)    [junit4]     @ com.carrotsearch.ant.tasks.junit4.localslavestreamhandler$2.run(localslavestreamhandler.java:122)    [junit4] jvm j0:     0.82 ..  1838.85 =  1838.03s    [junit4] execution time total: 30 minutes 38 seconds    [junit4] tests summary: 4 suites, 479 tests, 1 suite-level error, 1 error, 14 ignored (14 assumptions)  :distribution:integ-test-zip:integtestrunner failed  cluster distribution_integ-test-zip_integtestcluster - node 0 log excerpt: (full log @ d:\code\elasticsearch\distribution\integ-test-zip\build\cluster\integtestcluster node0\elasticsearch-7.0.0-alpha1-snapshot\logs\distribution_integ-test-zip_integtestcluster.log) ----------------------------------------- [2017-08-19t13:27:20,788][info ][o.e.n.node               ] [node-0] initializing ... [2017-08-19t13:27:21,939][info ][o.e.e.nodeenvironment    ] [node-0] using [1] data paths, mounts [[data (d:)]], net usable_space [463.9gb], net total_space [537.7gb], types [ntfs] [2017-08-19t13:27:21,940][info ][o.e.e.nodeenvironment    ] [node-0] heap size [494.9mb], compressed ordinary object pointers [true] [2017-08-19t13:27:21,952][info ][o.e.n.node               ] [node-0] node name [node-0], node id [rdzeumuztdkvkkz-jfmqvq] [2017-08-19t13:27:21,954][info ][o.e.n.node               ] [node-0] version[7.0.0-alpha1-snapshot], pid[10212], build[96b0d3e/2017-08-19t09:59:15.791z], os[windows 10/10.0/amd64], jvm[oracle corporation/java hotspot(tm) 64-bit server vm/1.8.0_66/25.66-b18] [2017-08-19t13:27:21,960][info ][o.e.n.node               ] [node-0] jvm arguments [-xms1g, -xmx1g, -xx:+useconcmarksweepgc, -xx:cmsinitiatingoccupancyfraction=75, -xx:+usecmsinitiatingoccupancyonly, -xx:+alwayspretouch, -xss1m, -djava.awt.headless=true, -dfile.encoding=utf-8, -djna.nosys=true, -xx:-omitstacktraceinfastthrow, -djdk.io.permissionsusecanonicalpath=true, -dio.netty.nounsafe=true, -dio.netty.nokeysetoptimization=true, -dio.netty.recycler.maxcapacityperthread=0, -dlog4j.shutdownhookenabled=false, -dlog4j2.disable.jmx=true, -xx:+heapdumponoutofmemoryerror, -xms512m, -xmx512m, -ea, -esa, -delasticsearch, -des.path.home=d:\code\elasticsearch\distribution\integ-test-zip\build\cluster\integtestcluster node0\elasticsearch-7.0.0-alpha1-snapshot, -des.path.conf=d:\code\elasticsearch\distribution\integ-test-zip\build\cluster\integtestcluster node0\elasticsearch-7.0.0-alpha1-snapshot\config] [2017-08-19t13:27:21,962][warn ][o.e.n.node               ] [node-0] version [7.0.0-alpha1-snapshot] pre-release version of elasticsearch , not suitable production [2017-08-19t13:27:22,722][info ][o.e.p.pluginsservice     ] [node-0] loaded module [transport-netty4] [2017-08-19t13:27:22,723][info ][o.e.p.pluginsservice     ] [node-0] no plugins loaded [2017-08-19t13:27:27,628][info ][o.e.d.discoverymodule    ] [node-0] using discovery type [zen] [2017-08-19t13:27:28,970][info ][o.e.n.node               ] [node-0] initialized [2017-08-19t13:27:28,971][info ][o.e.n.node               ] [node-0] starting ... [2017-08-19t13:27:30,355][info ][o.e.t.transportservice   ] [node-0] publish_address {127.0.0.1:57028}, bound_addresses {127.0.0.1:57028}, {[::1]:57029} [2017-08-19t13:27:33,508][info ][o.e.c.s.masterservice    ] [node-0] zen-disco-elected-as-master ([0] nodes joined), reason: new_master {node-0}{rdzeumuztdkvkkz-jfmqvq}{xhozx-qzshg8xxaol46vkq}{127.0.0.1}{127.0.0.1:57028}{testattr=test} [2017-08-19t13:27:33,520][info ][o.e.c.s.clusterapplierservice] [node-0] new_master {node-0}{rdzeumuztdkvkkz-jfmqvq}{xhozx-qzshg8xxaol46vkq}{127.0.0.1}{127.0.0.1:57028}{testattr=test}, reason: apply cluster state (from master [master {node-0}{rdzeumuztdkvkkz-jfmqvq}{xhozx-qzshg8xxaol46vkq}{127.0.0.1}{127.0.0.1:57028}{testattr=test} committed version [1] source [zen-disco-elected-as-master ([0] nodes joined)]]) [2017-08-19t13:27:33,644][info ][o.e.g.gatewayservice     ] [node-0] recovered [0] indices cluster_state ========================================= :distribution:integ-test-zip:integtestcluster#stop :distribution:zip:integtestcluster#stop :docs:integtestcluster#stop  failure: build failed exception.  * went wrong: execution failed task ':distribution:integ-test-zip:integtestrunner'. > there test failures: 4 suites, 479 tests, 1 suite-level error, 1 error, 14 ignored (14 assumptions) [seed: e53884aa64085b30]  * try: run --stacktrace option stack trace. run --info or --debug option more log output.  build failed  total time: 2 hrs 3 mins 42.667 secs 

because executing tests took long, run 1 test failed. can done easily, problem don't know 1 failed. says what went wrong: failed task ':distribution:integ-test-zip:integtestrunner'. error stacktrace seemingly infinite. goes until out of screen. there errors in logs, can't find test name.

is there way of figuring out test case failed?


Comments

Popular posts from this blog

ubuntu - PHP script to find files of certain extensions in a directory, returns populated array when run in browser, but empty array when run from terminal -

php - How can i create a user dashboard -

javascript - How to detect toggling of the fullscreen-toolbar in jQuery Mobile? -