[
https://issues.apache.org/jira/browse/IMPALA-13204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17866553#comment-17866553
]
gaurav singh commented on IMPALA-13204:
---------------------------------------
We observed that the setting of mysqld had issues in different environments due
to third party dependancies, permissions, docker etc. Hence we skip the mysql
test if the env setup is failed due to the following reasons:
1. These tests require to add the docker to be added to sudoer's group.
2. Can't connect to local MySQL server.
3. File /var/run/mysqld/mysqld.sock not found.
However, once the setup is completed and we do not see the expected results,
then we mark the test as "failed".
> MySQL setup process in _setup_mysql_test_env is flaky
> -----------------------------------------------------
>
> Key: IMPALA-13204
> URL: https://issues.apache.org/jira/browse/IMPALA-13204
> Project: IMPALA
> Issue Type: Bug
> Affects Versions: Impala 4.5.0
> Reporter: Laszlo Gaal
> Assignee: gaurav singh
> Priority: Major
> Labels: broken-build
>
> A failure during setup disables some test steps dynamically; however, this
> generates a JUnitXml symptom file, marking the build unstable. This shows up
> on the dashboard as a failure.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
