[ 
https://issues.apache.org/jira/browse/KUDU-3065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17938357#comment-17938357
 ] 

Alexey Serbin edited comment on KUDU-3065 at 3/25/25 9:24 PM:
--------------------------------------------------------------

One more example of the test scenario's output when failing (ASAN build):
{noformat}
src/kudu/integration-tests/master_replication-itest.cc:579: Failure
Expected: (val) > (0), actual: 0 vs 0
/home/jenkins-slave/workspace/build_and_test@2/src/kudu/util/test_util.cc:403: 
Failure
FailedTimed out waiting for assertion to pass.  
{noformat}

Full log is attached: [^master_replication-itest.00.txt.xz] 


was (Author: aserbin):
One more example of the test scenario's output when failing:
{noformat}
src/kudu/integration-tests/master_replication-itest.cc:579: Failure
Expected: (val) > (0), actual: 0 vs 0
/home/jenkins-slave/workspace/build_and_test@2/src/kudu/util/test_util.cc:403: 
Failure
FailedTimed out waiting for assertion to pass.  
{noformat}

Full log is attached: [^master_replication-itest.00.txt.xz] 

> MasterReplicationAndRpcSizeLimitTest.TabletReports sometimes fails
> ------------------------------------------------------------------
>
>                 Key: KUDU-3065
>                 URL: https://issues.apache.org/jira/browse/KUDU-3065
>             Project: Kudu
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 1.12.0
>            Reporter: Alexey Serbin
>            Priority: Major
>         Attachments: master_replication-itest.00.txt.xz, 
> master_replication-itest.txt.xz
>
>
> The {{MasterReplicationAndRpcSizeLimitTest.TabletReports}} scenario sometimes 
> fails with an error like below:
> {noformat}
> F0228 19:57:29.566195   236 test_workload.cc:330] Timed out: Timed out 
> waiting for Table Creation
> *** Check failure stack trace: ***
> *** Aborted at 1582919849 (unix time) try "date -d @1582919849" if you are 
> using GNU date ***
> PC: @     0x7f62a6483c37 gsignal
> *** SIGABRT (@0x3e8000000ec) received by PID 236 (TID 0x7f62ab9ff8c0) from 
> PID 236; stack trace: ***
>     @     0x7f62a94ca330 (unknown) at ??:0
>     @     0x7f62a6483c37 gsignal at ??:0
>     @     0x7f62a6487028 abort at ??:0
>     @     0x7f62a74f2e09 google::logging_fail() at ??:0
>     @     0x7f62a74f462d google::LogMessage::Fail() at ??:0
>     @     0x7f62a74f664c google::LogMessage::SendToLog() at ??:0
>     @     0x7f62a74f4189 google::LogMessage::Flush() at ??:0
>     @     0x7f62a74f6fdf google::LogMessageFatal::~LogMessageFatal() at ??:0
>     @     0x7f62ab5bf008 kudu::TestWorkload::Setup() at ??:0
>     @           0x431230 
> kudu::master::MasterReplicationAndRpcSizeLimitTest_TabletReports_Test::TestBody()
>  at src/kudu/integration-tests/master_replication-itest.cc:597
>     @     0x7f62a851ab89 
> testing::internal::HandleExceptionsInMethodIfSupported<>() at ??:0
>     @     0x7f62a850b68f testing::Test::Run() at ??:0
>     @     0x7f62a850b74d testing::TestInfo::Run() at ??:0
>     @     0x7f62a850b865 testing::TestCase::Run() at ??:0
>     @     0x7f62a850bb28 testing::internal::UnitTestImpl::RunAllTests() at 
> ??:0
>     @     0x7f62a850bdc9 testing::UnitTest::Run() at ??:0
>     @     0x7f62ab297cf3 RUN_ALL_TESTS() at ??:0
>     @     0x7f62ab295cab main at ??:0
>     @     0x7f62a646ef45 __libc_start_main at ??:0
>     @           0x42a999 (unknown) at ??:?
> W0228 19:57:29.694170  6801 catalog_manager.cc:4593] T 
> 00000000000000000000000000000000 P d48d9641d5694fa783f13d0dce1ad5a9: Tablet 
> 0113c6c5ccda4639a20e6cda5ce67acf (table test-workload 
> [id=1f40b8e5e9454964ad4380766e8e2382]) was not created within the allowed 
> timeout. Replacing with a new tablet 85e9b58f383a48cd807f7a49c6190867
> {noformat}
> The log is attached.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to