Bug 14594 - AB-INT meta-aws: sysroot setscene tasks fail
Summary: AB-INT meta-aws: sysroot setscene tasks fail
Status: RESOLVED DUPLICATE of bug 14680
Alias: None
Product: Other YP Layers
Classification: Build System, Metadata & Runtime
Component: layers (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium normal
Target Milestone: 4.0
Assignee: Richard Elberger
QA Contact:
URL:
Whiteboard: AB-INT
Depends on:
Blocks:
 
Reported: 2021-10-11 12:37 UTC by Thomas Perrot
Modified: 2022-01-13 00:27 UTC (History)
6 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Perrot 2021-10-11 12:37:39 UTC 
https://autobuilder.yoctoproject.org/typhoon/#/builders/122/builds/330/steps/17/logs/stdio

meta-aws ubuntu1604-ty-1


NOTE: recipe aws-iot-device-sdk-cpp-v2-1.14.1-r0: task do_populate_lic_setscene: Succeeded
WARNING: Logfile for failed setscene task is /home/pokybuild/yocto-worker/meta-aws/build/build/tmp/work/cortexa57-poky-linux/aws-iot-device-sdk-cpp-v2/1.14.1-r0/temp/log.do_package_write_deb_setscene.9786
WARNING: Setscene task (/home/pokybuild/yocto-worker/meta-aws/build/meta-aws/recipes-sdk/aws-iot-device-sdk-cpp-v2/aws-iot-device-sdk-cpp-v2_1.14.1.bb:do_package_write_deb_setscene) failed with exit code '1' - real task will be run instead
WARNING: Logfile for failed setscene task is /home/pokybuild/yocto-worker/meta-aws/build/build/tmp/work/cortexa57-poky-linux/aws-iot-device-sdk-cpp-v2/1.14.1-r0/temp/log.do_package_write_rpm_setscene.9788
WARNING: Setscene task (/home/pokybuild/yocto-worker/meta-aws/build/meta-aws/recipes-sdk/aws-iot-device-sdk-cpp-v2/aws-iot-device-sdk-cpp-v2_1.14.1.bb:do_package_write_rpm_setscene) failed with exit code '1' - real task will be run instead
WARNING: Logfile for failed setscene task is /home/pokybuild/yocto-worker/meta-aws/build/build/tmp/work/cortexa57-poky-linux/aws-iot-device-sdk-cpp-v2/1.14.1-r0/temp/log.do_package_write_ipk_setscene.9787
WARNING: Setscene task (/home/pokybuild/yocto-worker/meta-aws/build/meta-aws/recipes-sdk/aws-iot-device-sdk-cpp-v2/aws-iot-device-sdk-cpp-v2_1.14.1.bb:do_package_write_ipk_setscene) failed with exit code '1' - real task will be run instead
WARNING: Logfile for failed setscene task is /home/pokybuild/yocto-worker/meta-aws/build/build/tmp/work/cortexa57-poky-linux/aws-iot-device-sdk-cpp-v2/1.14.1-r0/temp/log.do_populate_sysroot_setscene.9790
WARNING: Setscene task (/home/pokybuild/yocto-worker/meta-aws/build/meta-aws/recipes-sdk/aws-iot-device-sdk-cpp-v2/aws-iot-device-sdk-cpp-v2_1.14.1.bb:do_populate_sysroot_setscene) failed with exit code '1' - real task will be run instead
WARNING: Logfile for failed setscene task is /home/pokybuild/yocto-worker/meta-aws/build/build/tmp/work/cortexa57-poky-linux/aws-iot-device-sdk-cpp-v2/1.14.1-r0/temp/log.do_package_qa_setscene.9785
WARNING: Setscene task (/home/pokybuild/yocto-worker/meta-aws/build/meta-aws/recipes-sdk/aws-iot-device-sdk-cpp-v2/aws-iot-device-sdk-cpp-v2_1.14.1.bb:do_package_qa_setscene) failed with exit code '1' - real task will be run instead
NOTE: Running setscene task 131 of 231 (/home/pokybuild/yocto-worker/meta-aws/build/meta-aws/recipes-sdk/aws-iot-device-sdk-cpp-v2/aws-iot-device-sdk-cpp-v2_1.14.1.bb:do_packagedata_setscene)
NOTE: recipe aws-iot-device-sdk-cpp-v2-1.14.1-r0: task do_packagedata_setscene: Started
WARNING: Logfile for failed setscene task is /home/pokybuild/yocto-worker/meta-aws/build/build/tmp/work/cortexa57-poky-linux/aws-iot-device-sdk-cpp-v2/1.14.1-r0/temp/log.do_packagedata_setscene.9852
WARNING: Setscene task (/home/pokybuild/yocto-worker/meta-aws/build/meta-aws/recipes-sdk/aws-iot-device-sdk-cpp-v2/aws-iot-device-sdk-cpp-v2_1.14.1.bb:do_packagedata_setscene) failed with exit code '1' - real task will be run instead
NOTE: Running setscene task 132 of 231 (/home/pokybuild/yocto-worker/meta-aws/build/meta-aws/recipes-sdk/aws-iot-device-sdk-cpp-v2/aws-iot-device-sdk-cpp-v2_1.14.1.bb:do_package_setscene)
NOTE: recipe aws-iot-device-sdk-cpp-v2-1.14.1-r0: task do_package_setscene: Started
WARNING: Logfile for failed setscene task is /home/pokybuild/yocto-worker/meta-aws/build/build/tmp/work/cortexa57-poky-linux/aws-iot-device-sdk-cpp-v2/1.14.1-r0/temp/log.do_package_setscene.9872
WARNING: Setscene task (/home/pokybuild/yocto-worker/meta-aws/build/meta-aws/recipes-sdk/aws-iot-device-sdk-cpp-v2/aws-iot-device-sdk-cpp-v2_1.14.1.bb:do_package_setscene) failed with exit code '1' - real task will be run instead
NOTE: Running setscene task 133 of 231 (/home/pokybuild/yocto-worker/meta-aws/build/meta-aws/recipes-sdk/aws-c-iot/aws-c-iot_0.0.7.bb:do_packagedata_setscene)
NOTE: Running setscene task 134 of 231 (/home/pokybuild/yocto-worker/meta-aws/build/meta-aws/recipes-sdk/aws-c-iot/aws-c-iot_0.0.7.bb:do_populate_sysroot_setscene)
NOTE: Running setscene task 135 of 231 (/home/pokybuild/yocto-worker/meta-aws/build/meta-aws/recipes-sdk/aws-iot-device-sdk-cpp-v2/aws-iot-device-sdk-cpp-v2_1.14.1.bb:do_deploy_source_date_epoch_setscene)
NOTE: recipe aws-iot-device-sdk-cpp-v2-1.14.1-r0: task do_deploy_source_date_epoch_setscene: Started
Comment 1 Thomas Perrot 2021-10-11 12:41:10 UTC 
https://autobuilder.yoctoproject.org/typhoon/#/builders/122/builds/330/steps/13/logs/stdio

meta-aws qemux86-64 ubuntu1604-ty-1
Comment 2 Richard Purdie 2021-10-11 15:21:32 UTC 
All the recipes showing warnings have SRC_URIs setting tags for revisions. These need to be resolved in the upstream git repo to revisions. I suspect some connection issue happened to github.com meaning these all failed. It could be protection on the github side from too many requests.
Comment 3 Richard Elberger 2021-10-11 19:22:38 UTC 
This might be an itermittent network issue or momentary routing issue - and in a separate thread it was mentioned that this could be a throttling issue.  What is the build engineering practice for narrowing this problem when running from a YP infrastructure context?
Comment 4 Richard Purdie 2021-10-12 13:33:18 UTC 
Out initial policy is monitoring to evaluate the frequency. We are doing this by opening the bug and logging occurrences. Our sysadmin is also investigating whether there are any network issues which could account for the issue. Beyond that we're not sure how to proceed.
Comment 5 Alexandre Belloni 2022-01-13 00:27:19 UTC 
14680 shows this doesn't only affect meta-aws

*** This bug has been marked as a duplicate of bug 14680 ***