Bug 14318

Summary:	do_unpack failure during test_devtool_kernelmodule
Product:	[Build System, Metadata & Runtime] OE-Core	Reporter:	Oleksiy Obitotskyy <oobitots>
Component:	core	Assignee:	Unassigned <unassigned>
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	normal
Priority:	Medium+	CC:	meta.mr.watcher, meta.watcher, mhalstead, poky.bs.watcher, poky.watcher, randy.macleod
Version:	3.3
Target Milestone:	3.3 M4
Hardware:	x86
OS:	Multiple
Whiteboard:	AB-INT
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	Don't know

Description Oleksiy Obitotskyy 2021-03-23 09:42:22 UTC

https://autobuilder.yoctoproject.org/typhoon/#/builders/63/builds/3198

NOTE: recipe linux-yocto-5.10.21+gitAUTOINC+8c8f6a791b_8c516ced69-r0: task do_unpack: Started
ERROR: linux-yocto-5.10.21+gitAUTOINC+8c8f6a791b_8c516ced69-r0 do_unpack: Unpack failure for URL: 'git://git.yoctoproject.org/linux-yocto.git;name=machine;branch=v5.10/standard/qemuppc;'. No up to date source found: clone directory not available or not up to date: /home/pokybuild/yocto-worker/qemuppc/build/build/tmp/work/qemuppc-poky-linux/core-image-sato/1.0-r0/testsdkext/downloads/git2/git.yoctoproject.org.linux-yocto.git; shallow clone not enabled
ERROR: Logfile of failure stored in: /home/pokybuild/yocto-worker/qemuppc/build/build/tmp/work/qemuppc-poky-linux/core-image-sato/1.0-r0/testsdkext/tmp/work/qemuppc-poky-linux/linux-yocto/5.10.21+gitAUTOINC+8c8f6a791b_8c516ced69-r0/temp/log.do_unpack.16752
NOTE: recipe linux-yocto-5.10.21+gitAUTOINC+8c8f6a791b_8c516ced69-r0: task do_unpack: Failed
ERROR: Task (/home/pokybuild/yocto-worker/qemuppc/build/build/tmp/work/qemuppc-poky-linux/core-image-sato/1.0-r0/testsdkext/layers/build/meta/recipes-kernel/linux/linux-yocto_5.10.bb:do_unpack) failed with exit code '1'
...
NOTE: recipe core-image-sato-1.0-r0: task do_testsdk: Succeeded
Traceback (most recent call last):
  File "/home/pokybuild/yocto-worker/qemuppc/build/meta/lib/oeqa/sdkext/cases/devtool.py", line 86, in test_devtool_kernelmodule
    self._run('devtool build %s' % recipe)
  File "/home/pokybuild/yocto-worker/qemuppc/build/meta/lib/oeqa/sdkext/case.py", line 22, in _run
    return subprocess.check_output(". %s > /dev/null;"\
  File "/home/pokybuild/yocto-worker/qemuppc/build/buildtools/sysroots/x86_64-pokysdk-linux/usr/lib/python3.9/subprocess.py", line 420, in check_output
    return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
  File "/home/pokybuild/yocto-worker/qemuppc/build/buildtools/sysroots/x86_64-pokysdk-linux/usr/lib/python3.9/subprocess.py", line 524, in run
    raise CalledProcessError(retcode, process.args,
oeqa.utils.subprocesstweak.OETestCalledProcessError: Command '. /home/pokybuild/yocto-worker/qemuppc/build/build/tmp/work/qemuppc-poky-linux/core-image-sato/1.0-r0/testsdkext/environment-setup-ppc7400-poky-linux > /dev/null; devtool build kernel-module-hello-world;' returned non-zero exit status 1
...
RESULTS - devtool.DevtoolTest.test_devtool_kernelmodule: ERROR (351.02s)
SUMMARY:
core-image-sato esdk (poky-glibc-x86_64-core-image-sato-ppc7400-qemuppc-toolchain-ext-3.2+snapshot.sh:environment-setup-ppc7400-poky-linux) - Ran 21 tests in 1164.717s
core-image-sato esdk - FAIL - Required tests failed (successes=15, skipped=5, failures=0, errors=1)
ERROR: core-image-sato-1.0-r0 do_testsdkext: core-image-sato - FAILED - check the task log and the commands log
ERROR: Logfile of failure stored in: /home/pokybuild/yocto-worker/qemuppc/build/build/tmp/work/qemuppc-poky-linux/core-image-sato/1.0-r0/temp/log.do_testsdkext.48071
NOTE: recipe core-image-sato-1.0-r0: task do_testsdkext: Failed
ERROR: Task (/home/pokybuild/yocto-worker/qemuppc/build/meta/recipes-sato/images/core-image-sato.bb:do_testsdkext) failed with exit code '1

Comment 1 Randy MacLeod 2021-03-25 14:56:22 UTC

What there a change going on, on the git server when this happened?

Comment 2 Stephen K Jolley 2021-03-25 15:23:38 UTC

There was some activity on the infrastructure but apparently not directly related to this failure. Re-open if it happens again.

Comment 3 Michael Halstead 2021-03-25 16:46:41 UTC

There are several requests in the logs around this time indicating the server was being scanned for vulnerabilities. No vulnerabilities were found but the scan caused a few timeouts.