You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kudu.apache.org by in...@openlabtesting.org on 2020/08/02 09:17:23 UTC
Daily KUDU ARM64 Cron Job Test Result - FAILED
Build failed.
- kudu-build-test-arm64-in-docker https://logs.openlabtesting.org/logs/periodic-kudu-mail/github.com/apache/kudu/master/kudu-build-test-arm64-in-docker/a8a395b/ : FAILURE in 2h 51m 30s
Re: Daily KUDU ARM64 Cron Job Test Result - FAILED
Posted by Andrew Wong <aw...@cloudera.com.INVALID>.
This failure seems to have been caused by flakiness in initializing the
Kudu service in Ranger, and doesn't seem like it would be specific to ARM
deployments:
I0802 07:50:56.734228 14453 mini_ranger.cc:234] Ranger bound to 35657
I0802 07:50:56.734279 14453 mini_ranger.cc:235] Ranger admin URL:
http://127.14.29.84:35559
I0802 07:50:56.734333 14453 mini_ranger.cc:163] Time spent starting
Ranger: real 30.209s user 0.000s sys 0.106s
/opt/kudu/src/kudu/integration-tests/external_mini_cluster-itest-base.cc:66:
Failure
Failed
Bad status: Network error: Failed to start the Ranger service: Failed
to create Kudu service: Error recceived from Ranger: : curl error:
Couldn't connect to server: Failed to connect to 127.14.29.84 port
35559: Connection refused
/opt/kudu/src/kudu/integration-tests/master_authz-itest.cc:584: Failure
Expected: StartClusterWithOpts(std::move(opts)) doesn't generate new
fatal failures in the current thread.
Actual: it does.
/opt/kudu/src/kudu/integration-tests/master_authz-itest.cc:731: Failure
Expected: SetUpCluster(GetParam()) doesn't generate new fatal failures
in the current thread.
Actual: it does.
I0802 07:50:56.735337 14453 external_mini_cluster-itest-base.cc:80]
Found fatal failure
I0802 07:50:56.735864 14453 mini_ranger.cc:65] Stopping Ranger...
I0802 07:50:57.169780 14453 mini_ranger.cc:67] Stopped Ranger
2020-08-02 07:50:57.169 UTC [14490] LOG: received smart shutdown request
2020-08-02 07:50:57.173 UTC [14490] LOG: background worker "logical
replication launcher" (PID 14499) exited with exit code 1
2020-08-02 07:50:57.174 UTC [14494] LOG: shutting down
2020-08-02 07:50:57.273 UTC [14490] LOG: database system is shut down
2020-08-02T07:50:57Z chronyd exiting
I0802 07:50:57.292048 14453 test_util.cc:145]
-----------------------------------------------
I0802 07:50:57.292080 14453 test_util.cc:146] Had fatal failures,
leaving test files at
/tmp/kudutest-0/master_authz-itest.6.AuthzProviders_MasterAuthzITest.TestAuthzListTablesConcurrentRename_Ranger.1596354624466323-14453
[ FAILED ] AuthzProviders/MasterAuthzITest.TestAuthzListTablesConcurrentRename/Ranger,
where GetParam() = 0 (32819 ms)
We should probably add some retries into this snippet, assuming the issue
is the Ranger webserver not being immediately operational.
On Sun, Aug 2, 2020 at 2:17 AM <in...@openlabtesting.org> wrote:
> Build failed.
>
> - kudu-build-test-arm64-in-docker
> https://logs.openlabtesting.org/logs/periodic-kudu-mail/github.com/apache/kudu/master/kudu-build-test-arm64-in-docker/a8a395b/
> : FAILURE in 2h 51m 30s
>
--
Andrew Wong