Joe McDonnell created IMPALA-11379:
--------------------------------------
Summary: 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
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-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
