@@ -852,9 +852,9 @@ Once this is completed, you may run it like this:
852852 --cluster true
853853
854854For possible ` javaOptions` see
855- [arangodb-java-driver/dev-README.md#test-provided-deployment](https://github.com/arangodb/arangodb-java-driver/blob/next/arangodb-java-driver /dev-README.md)
855+ [arangodb-java-driver/dev-README.md#test-provided-deployment](https://github.com/arangodb/arangodb-java-driver/blob/master /dev-README.md)
856856in the java source, or the
857- [surefire documentation](https://maven.apache.org/surefire/maven-surefire-plugin/examples/single-test.html]
857+ [surefire documentation](https://maven.apache.org/surefire/maven-surefire-plugin/examples/single-test.html)
858858
859859#### ArangoJS
860860
@@ -931,13 +931,24 @@ Debugging rspec with gdb:
931931
932932 server> ./ scripts/ unittest http_server -- test api- import -spec.rb --server tcp:// 127.0.0.1:7777
933933 - or -
934- server> ARANGO_SERVER = " 127.0.0.1:6666" rspec - Itests/ rb/ HttpInterface -- format d -- color tests/ rb/ HttpInterface/ api- import -spec.rb
934+ server> ARANGO_SERVER = " 127.0.0.1:6666" \
935+ rspec - Itests/ rb/ HttpInterface -- format d \
936+ -- color tests/ rb/ HttpInterface/ api- import -spec.rb
935937
936- client> gdb -- args ./ build/ bin/ arangod -- server .endpoint http+ tcp: // 127.0.0.1:6666 --server.authentication false --log.level communication=trace ../arangodb-data-test-mmfiles
938+ client> gdb -- args ./ build/ bin/ arangod -- server .endpoint http+ tcp: // 127.0.0.1:6666 \
939+ -- server .authentication false \
940+ -- log .level communication= trace \
941+ ../ arangodb- data- test
937942
938943Debugging a storage engine:
939944
940- host> rm - fr ../ arangodb- data- rocksdb/ ; gdb -- args ./ build/ bin/ arangod -- console -- server .storage - engine rocksdb -- foxx .queues false -- server .statistics false -- server .endpoint http+ tcp: // 0.0.0.0:7777 ../arangodb-data-rocksdb
945+ host> rm - fr ../ arangodb- data- rocksdb/ ; \
946+ gdb -- args ./ build/ bin/ arangod \
947+ -- console \
948+ -- foxx .queues false \
949+ -- server .statistics false \
950+ -- server .endpoint http+ tcp: // 0.0.0.0:7777 \
951+ ../ arangodb- data- rocksdb
941952 (gdb) catch throw
942953 (gdb) r
943954 arangod> require (" jsunity" ).runTest (" tests/js/client/shell/shell-client.js" );
@@ -994,6 +1005,69 @@ Currently available Analyzers are:
9941005 - locateShortServerLife - whether the servers lifetime for the tests isn' t at least 10 times as long as startup/shutdown
9951006 - locateLongSetupTeardown - locate tests that may use a lot of time in setup/teardown
9961007 - yaml - dumps the json file as a yaml file
997-
1008+ - unitTestTabularPrintResults - prints a table, add one (or more) of the following columns to print by adding it to `--tableColumns`:
1009+ - `duration` - the time spent in the complete testfile
1010+ - `status` - sucess/fail
1011+ - `failed` - fail?
1012+ - `total` - the time spent in the testcase
1013+ - `totalSetUp` - the time spent in setup summarized
1014+ - `totalTearDown` - the time spent in teardown summarized
1015+ - `processStats.sum_servers.minorPageFaults` - Delta run values from `/proc/<pid>/io` summarized over all instances
1016+ - `processStats.sum_servers.majorPageFaults` -
1017+ - `processStats.sum_servers.userTime` -
1018+ - `processStats.sum_servers.systemTime` -
1019+ - `processStats.sum_servers.numberOfThreads` -
1020+ - `processStats.sum_servers.residentSize` -
1021+ - `processStats.sum_servers.residentSizePercent` -
1022+ - `processStats.sum_servers.virtualSize` -
1023+ - `processStats.sum_servers.rchar` -
1024+ - `processStats.sum_servers.wchar` -
1025+ - `processStats.sum_servers.syscr` -
1026+ - `processStats.sum_servers.syscw` -
1027+ - `processStats.sum_servers.read_bytes` -
1028+ - `processStats.sum_servers.write_bytes` -
1029+ - `processStats.sum_servers.cancelled_write_bytes` -
1030+ - `processStats.sum_servers.sockstat_sockets_used` - Absolute values from `/proc/<pid>/net/sockstat` summarized over all instances
1031+ - `processStats.sum_servers.sockstat_TCP_inuse` -
1032+ - `processStats.sum_servers.sockstat_TCP_orphan` -
1033+ - `processStats.sum_servers.sockstat_TCP_tw` -
1034+ - `processStats.sum_servers.sockstat_TCP_alloc` -
1035+ - `processStats.sum_servers.sockstat_TCP_mem` -
1036+ - `processStats.sum_servers.sockstat_UDP_inuse` -
1037+ - `processStats.sum_servers.sockstat_UDP_mem` -
1038+ - `processStats.sum_servers.sockstat_UDPLITE_inuse` -
1039+ - `processStats.sum_servers.sockstat_RAW_inuse` -
1040+ - `processStats.sum_servers.sockstat_FRAG_inuse` -
1041+ - `processStats.sum_servers.sockstat_FRAG_memory` -
1042+
1043+ Process stats are kept by process.
1044+ So if your DB-Server had the PID `1721882`, you can dial its values by specifying
1045+ `processStats.1721882_dbserver.sockstat_TCP_tw`
1046+ into the generated table.
1047+
1048+ i.e.
9981049
9991050 ./scripts/examine_results.js -- ' yaml,locateLongRunning' --readFile out/UNITTEST_RESULT.json
1051+
1052+ or:
1053+
1054+ ./scripts/examine_results.js -- ' unitTestTabularPrintResults' \
1055+ --readFile out/UNITTEST_RESULT.json \
1056+ --tableColumns ' duration,processStats .sum_servers .sockstat_TCP_orphan ,processStats .sum_servers .sockstat_TCP_tw
1057+
1058+ revalidating one testcase using jq:
1059+
1060+ jq ' .shell_client."enterprise/tests/js/common/shell/smart-graph-enterprise-cluster.js"' < \
1061+ out/ UNITTEST_RESULT .json | grep sockstat_TCP_tw
1062+
1063+ getting the PIDs of the server in the testrun using jq:
1064+
1065+ jq ' .shell_client."enterprise/tests/js/common/shell/smart-graph-enterprise-cluster.js"' < \
1066+ out/ UNITTEST_RESULT .json | grep ' "[0-9]*_[agent|dbserver|coordinator]'
1067+ " 1721674_agent" : {
1068+ " 1721675_agent" : {
1069+ " 1721676_agent" : {
1070+ " 1721882_dbserver" : {
1071+ " 1721883_dbserver" : {
1072+ " 1721884_dbserver" : {
1073+ " 1721885_coordinator" : {
0 commit comments