You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Quanlong Huang (Jira)" <ji...@apache.org> on 2022/05/16 02:55:00 UTC

[jira] [Commented] (IMPALA-11291) minidump-test is flaky

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

Quanlong Huang commented on IMPALA-11291:
-----------------------------------------

The output could contains lines like "22/05/16 10:49:51 INFO util.JvmPauseMonitor: Starting JVM pause monitor". It can be at any position including the middle of an expected line. E.g.
{code}
22/05/16 10:19:44 INFO util.JvmPauseMonitor: Starting JVM pause monitor
Minidump in thread [27550] running query 0000000000000001:0000000000000002, fragment instance 0000000000000003:0000000000000004
Wrote minidump to /tmp/arbitrary/path/429f6f1b-57ca-41c7-e04bcebf-ef7246c5.dmp

{code}
or
{code}
Minidump in thread [14692] running query 0000000000000001:000000000000000222/05/16 10:49:51 INFO util.JvmPauseMonitor: Starting JVM pause monitor
, fragment instance 0000000000000003:0000000000000004
Wrote minidump to /tmp/arbitrary/path/0a3930a4-f95e-4d27-faa1f1a6-beacd4a1.dmp

{code}

> minidump-test is flaky
> ----------------------
>
>                 Key: IMPALA-11291
>                 URL: https://issues.apache.org/jira/browse/IMPALA-11291
>             Project: IMPALA
>          Issue Type: Bug
>            Reporter: Quanlong Huang
>            Assignee: Quanlong Huang
>            Priority: Major
>
> Minidump.DumpCallback and Minidump.DumpCallbackWithThread added by IMPALA-11275 are flaky.
> Minidump.DumpCallback is found to fail in an unrelated build:
> https://jenkins.impala.io/job/ubuntu-16.04-from-scratch/16449/testReport/junit/(root)/Minidump/DumpCallback/
> {noformat}
> /home/ubuntu/Impala/be/src/util/minidump-test.cc:47
> Value of: lines.size()
>   Actual: 4
> Expected: 3
> {noformat}
> While looping the test locally, I can also find failures of DumpCallbackWithThread:
> {code}
> seed = 1652667209
> Note: Google Test filter = Minidump.*
> [==========] Running 2 tests from 1 test case.
> [----------] Global test environment set-up.
> [----------] 2 tests from Minidump
> [ RUN      ] Minidump.DumpCallback
> [       OK ] Minidump.DumpCallback (1 ms)
> [ RUN      ] Minidump.DumpCallbackWithThread
> /home/quanlong/workspace/Impala/be/src/util/minidump-test.cc:76: Failure
> Value of: lines.size()
>   Actual: 4
> Expected: 3
> /home/quanlong/workspace/Impala/be/src/util/minidump-test.cc:77: Failure
> Value of: boost::regex_match(lines[0], minidump_in_thread)
>   Actual: false
> Expected: true
> /home/quanlong/workspace/Impala/be/src/util/minidump-test.cc:78: Failure
> Value of: boost::regex_match(lines[1], wrote_minidump)
>   Actual: false
> Expected: true
> /home/quanlong/workspace/Impala/be/src/util/minidump-test.cc:79: Failure
> Value of: lines[2]
>   Actual: "Wrote minidump to /tmp/arbitrary/path/b5cfb1b6-14cc-4a43-676f738b-52e07232.dmp"
> Expected: ""
> [  FAILED  ] Minidump.DumpCallbackWithThread (0 ms)
> [----------] 2 tests from Minidump (1 ms total)
> [----------] Global test environment tear-down
> [==========] 2 tests from 1 test case ran. (1 ms total)
> [  PASSED  ] 1 test.
> [  FAILED  ] 1 test, listed below:
> [  FAILED  ] Minidump.DumpCallbackWithThread
> {code}
> CC [~MikaelSmith]



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org