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 "ASF subversion and git services (Jira)" <ji...@apache.org> on 2022/06/23 00:22:00 UTC
[jira] [Commented] (IMPALA-11379) perf-AB-test Jenkins job fails with "Working copy is dirty"
[ https://issues.apache.org/jira/browse/IMPALA-11379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17557743#comment-17557743 ]
ASF subversion and git services commented on IMPALA-11379:
----------------------------------------------------------
Commit 7a26ff4b97603e60c91f5211e6e139affd213752 in impala's branch refs/heads/master from Joe McDonnell
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=7a26ff4b9 ]
IMPALA-11379: Remove kerberos.egg-info directory
This directory is currently checked in, but it is
overwritten when building the shell. On some Linux
distributions, the output is different from what
is checked in. This causes problems for perf-AB-test
(based on bin/single_node_perf_run.py), which relies on
a build not causing any modifications.
This removes the kerberos.egg-info directory,
which does not need to be checked in.
This also adds checks to the GVO Jenkins jobs
to verify that the source tree is unmodified after
bootstrap_build.sh and boostrap_development.sh.
These checks are not included in those scripts
directly, because developers can run those scripts
in their development environments, which may have
modifications.
Tests:
- Uploaded a change without removing the kerberos.egg-info
directory and verified that the new checks fail
- Verified that perf-AB-test gets past the current issue
Change-Id: I90b486bb6c1644fc18b56779d6c54e1e1b3c9aaa
Reviewed-on: http://gerrit.cloudera.org:8080/18650
Reviewed-by: Impala Public Jenkins <im...@cloudera.com>
Reviewed-by: Michael Smith <mi...@cloudera.com>
Tested-by: Impala Public Jenkins <im...@cloudera.com>
> perf-AB-test Jenkins job fails with "Working copy is dirty"
> -----------------------------------------------------------
>
> Key: IMPALA-11379
> URL: https://issues.apache.org/jira/browse/IMPALA-11379
> Project: IMPALA
> Issue Type: Bug
> Components: Infrastructure
> Affects Versions: Impala 4.2.0
> Reporter: Joe McDonnell
> Priority: Major
>
> When using the perf-AB-test job on upstream Jenkins, it fails with this message:
> {noformat}
> 14:50:56 + [[ ! -v HASH_B ]]
> 14:50:56 + [[ ! -v IMPALAD_ARGS ]]
> 14:50:56 + IMPALAD_ARGS=
> 14:50:56 + ./bin/single_node_perf_run.py --iterations 10 --scale 42 --table_formats parquet/none --workload tpch --num_impalads 3 --query_names '.*' --load --start_minicluster --impalad_args '' 66cde5ba8f707e61b1b46dabe114819de8b4f75d 06b1db4675b509b9461f7489d81a2c74930aa413
> 14:50:56 M shell/ext-py/kerberos-1.3.1/kerberos.egg-info/PKG-INFO
> 14:50:58 Traceback (most recent call last):
> 14:50:58 File "./bin/single_node_perf_run.py", line 359, in <module>
> 14:50:58 main()
> 14:50:58 File "./bin/single_node_perf_run.py", line 340, in main
> 14:50:58 raise Exception("Working copy is dirty. Consider 'git stash' and try again.")
> 14:50:58 Exception: Working copy is dirty. Consider 'git stash' and try again.{noformat}
> This is comparing the latest two master commits, and it seems to reproduce in general for everything. We should figure out how to fix this and add some check in GVO to prevent it in future.
--
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