[
https://issues.apache.org/jira/browse/IMPALA-12555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17785580#comment-17785580
]
ASF subversion and git services commented on IMPALA-12555:
----------------------------------------------------------
Commit 3be9b82207ddf32ca48ea1b2afbc88d8dffad8a4 in impala's branch
refs/heads/master from Laszlo Gaal
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=3be9b8220 ]
IMPALA-12555: Point Maven cache downloader to current location
bin/jenkins/populate_m2_directory.py is used during bootstrap_system.sh
to prime the local .m2 cache for Maven. This preloads the majority of
common Java dependencies for faster front-end builds.
The priming bundle is generated during nightly builds of the
'all-build-options' job running on the master branch. The downloader
script then reaches out to jenkins.impala.io to locate and download the
generated tarball.
This download has been failing for the past few weeks for a banal
reason: all the jobs for the upstream precommit environment were
migrated from Ubuntu 16.04 to Ubuntu 20.04, which was also reflected in
the job names. However, bin/jenkins/populate_m2_directory.py never
received the update to point it to the current version of the
all-build-options job, and the usable builds in the old location have
all aged out of Jenkins.
This patch points the job to the right location to restore cache
priming.
Change-Id: Id494fb7f24f1364a96526b440c8a0c4b6feda588
Reviewed-on: http://gerrit.cloudera.org:8080/20698
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> bin/jenkins/populate_m2_directory.py fails during bootstrap in recent builds
> ----------------------------------------------------------------------------
>
> Key: IMPALA-12555
> URL: https://issues.apache.org/jira/browse/IMPALA-12555
> Project: IMPALA
> Issue Type: Bug
> Affects Versions: Impala 4.4.0
> Reporter: Laszlo Gaal
> Assignee: Laszlo Gaal
> Priority: Critical
>
> All Impala precommit builds initialize their workers by running
> bin/bootstrap_system.sh. This script runs
> bin/jenkins/populate_m2_directory.py at the end to prime the local Maven
> cache for faster front-end builds.
> This script has been failing for some time now with the below pattern:
> {code}
> 00:03:20.298 ++ echo '>>> Populating m2 directory...'
> 00:03:20.298 >>> Populating m2 directory...
> 00:03:20.298 ++ bin/jenkins/populate_m2_directory.py
> 00:03:20.360 Could not find any m2 archive for jenkins.impala.io
> all-build-options-ub1604
> 00:03:20.360 Downloading m2 archive from None to /tmp/tmpAcvu5y
> 00:03:20.360 Traceback (most recent call last):
> 00:03:20.360 File "bin/jenkins/populate_m2_directory.py", line 173, in
> <module>
> 00:03:20.360 main()
> 00:03:20.360 File "bin/jenkins/populate_m2_directory.py", line 167, in main
> 00:03:20.360 download_and_unpack_m2_archive(m2_archive_url, tmpdir)
> 00:03:20.360 File "bin/jenkins/populate_m2_directory.py", line 146, in
> download_and_unpack_m2_archive
> 00:03:20.360 tarball_name = os.path.basename(url)
> 00:03:20.360 File "/usr/lib/python2.7/posixpath.py", line 114, in basename
> 00:03:20.360 i = p.rfind('/') + 1
> 00:03:20.360 AttributeError: 'NoneType' object has no attribute 'rfind'
> 00:03:20.362 ++ echo 'Failed to prepopulate the m2 directory. Continuing...'
> 00:03:20.362 Failed to prepopulate the m2 directory. Continuing...
> 00
> {code}
> The failure is caused by the script still trying to find the tarball in the
> Ubuntu 16.04 version of the {{all-build-options}} job, which was retired
> months ago.
> The script should be updated to point to the Ubuntu 20.04 version of the job.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
