February 25 Build Run Status #739

petefoth · 2025-01-31T16:19:31Z

New build server buildserv3

22.1 builds: 172 devices

Old build server buildserv2

18.1 devices: (removed caprip - it's a 22.1 device) a5y17lte,a7y17lte,addison,ahannah,albus,bacon,caprip,castor,castor_windy,cedric,d800,d801,d802,d803,d850,d851,d852,d855,debx,ether,f400,flox,FP2,ginkgo,griffin,hannah,hlte,hltechn,hltekor,hltetmo,jactivelte,jasmine_sprout,jason,jflteatt,jfltespr,jfltevzw,jfltexx,jfvelte,klte,klteactivexx,klteaio,kltechn,kltechnduo,klteduos,kltedv,kltekdi,kltekor,kugo,kuntao,lavender,lithium,ls990,m20lte,montana,obiwan,oneplus3,platina,rhannah,s3ve3gds,s3ve3gjv,s3ve3gxx,scorpio,shamu,sirius,suzu,twolip,victara,vs985,wayne,whyred,X00P,X01AD,X01BD,x2,YTX703F,YTX703L,z3,z3,z3c,zl,harpia
- unofficial: z3tc,z3tcw
19.1 devices:monet
21.0 devices: akari,akatsuki,alphaplus,apollon,aurora,betalm,billie,cmi,dre,earth,foster,foster_tab,gtowifi,joan,lmi,mh2lm,Mi439,Mi8917,Mi8937,miatoll,munch,nairo,NB1,nx611j,onclite,porg,porg_tab,quill,quill_tab,racer,sif,surya,thyme,umi,xz2c
- unofficial: lilac,poplar,poplar_dsds,maple,maple_dsds
22.0 devices: a21s,a52q,a52sxq,a71,a72q,a73xq,akita,alioth,aura,axolotl,barbet,beckham,berlin,berlna,beryllium,beyond0lte,beyond1lte,beyond2lte,beyondx,bluejay,blueline,bonito,borneo,bramble,bronco,caiman,caprip,cebu,channel,cheeseburger,cheetah,cheryl,chiron,comet,coral,crosshatch,d1,d1x,d2s,d2x,davinci,deadpool,devon,dipper,discovery,dopinder,DRG,dubai,dumpling,enchilada,eqs,equuleus,evert,f62,fajita,felix,flame,FP3,FP4,FP5,g710n,g710ulm,gauguin,gemini,grus,gta4l,gta4lwifi,gta4xl,gta4xlwifi,gts4lv,gts4lvwifi,guacamole,guacamoleb,guam,guamp,hawao,haydn,heart,hotdog,hotdogb,husky,ingot,instantnoodle,instantnoodlep,judyln,judyp,judypn,kane,kebab,kiev,kirin,komodo,lake,larry,lemonade,lemonadep,lemonades,lisa,luigi,lynx,m5,m5_tab,m52xq,marlin,mars,martini,mata,mermaid,messi,nash,natrium,nio,nx,nx_tab,nx606j,nx619j,ocean,odroidc4,odroidc4_tab,oriole,oscar,oscaro,panther,payton,pdx203,pdx206,pdx214,pdx215,pdx234,pdx237,perseus,pioneer,PL2,polaris,pro1,pro1x,pstar,pyxis,radxa0,radxa02,radxa0_tab,radxa02_tab,raven,redfin,renoir,rhode,river,rtwo,sabrina,sagit,sailfish,salami,sargo,shark,shiba,socrates,Spacewar,sunfish,sweet,taimen,tangorpro,TP1803,tokay,troika,ursa,vela,voyager,wade,walleye,xpeng,Z01R,zippo

The text was updated successfully, but these errors were encountered:

petefoth · 2025-02-02T07:47:11Z

Sun 02 Feb 25

buildserv3: Failed build for axolotl branch: lineage-22.1 - looks like transient problem connecting to github
>> [Sun Feb 2 01:01:42 UTC 2025] repo sync failed for axolotl, lineage-22.1 branch

>> [Sun Feb  2 00:54:34 UTC 2025] Syncing branch repository
error: Cannot fetch LineageOS/hudson from https://github.com/LineageOS/hudson
error: Cannot fetch LineageOS/android_packages_apps_AudioFX from https://github.com/LineageOS/android
_packages_apps_AudioFX

buildserv3: Failed build for beyond1lte branch: lineage-22.1

[ 99% 182333/183040] Target vbmeta image: out/target/product/beyond1lte/vbmeta.img (priority: 6)
FAILED: out/target/product/beyond1lte/vbmeta.img
/bin/bash -c "(mkdir -p out/target/product/beyond1lte/obj/avb_chain_keys ) && (out/host/linux-x86/bin/avbtool extract_public_key --key external/avb/test/data/testkey_rsa4096.pem --output  out/target/product/beyond1lte/obj/avb_chain_keys/recovery.avbpubkey ) && (out/host/linux-x86/bin/avbtool make_vbmeta_image --include_descriptors_from_image out/target/product/beyond1lte/boot.img --include_descriptors_from_image out/target/product/beyond1lte/system.img --include_descriptors_from_image out/target/product/beyond1lte/vendor.img --include_descriptors_from_image out/target/product/beyond1lte/product.img --include_descriptors_from_image out/target/product/beyond1lte/system_ext.img --include_descriptors_from_image out/target/product/beyond1lte/odm.img --include_descriptors_from_image out/target/product/beyond1lte/dtbo.img --algorithm SHA256_RSA4096 --key external/avb/test/data/testkey_rsa4096.pem --include_descriptors_from_image out/target/product/beyond1lte/dtb.img --flags 3 --padding_size 4096 --rollback_index 1736035200 --output out/target/product/beyond1lte/vbmeta.img ) && (rm -rf out/target/product/beyond1lte/obj/avb_chain_keys )"
/srv/src/LINEAGE_22_1/out/host/linux-x86/bin/avbtool: Given image does not look like a vbmeta image.

petefoth · 2025-02-05T06:25:50Z

Wed 05 Feb 25

buildserv3: Failed build for d1,d1x,d2s branch: lineage-22.1

[ 99% 182472/183180] Target vbmeta image: out/target/product/d1/vbmeta.img (priority: 6)
FAILED: out/target/product/d1/vbmeta.img
...
/srv/src/LINEAGE_22_1/out/host/linux-x86/bin/avbtool: Given image does not look like a vbmeta image

buildserv2: Failed build for x2 branch: lineage-18.1

[ 27% 230/845] including device/leeco/msm8996-common/Android.mk ...
FAILED:
In file included from build/make/core/package.mk:78:
In file included from device/leeco/msm8996-common/Android.mk:31:
In file included from device/leeco/msm8996-common/libhidl/Android.mk:22:
In file included from build/make/core/shared_library.mk:32:
In file included from build/make/core/shared_library_internal.mk:34:
In file included from build/make/core/dynamic_binary.mk:39:
In file included from build/make/core/binary.mk:9:
build/make/core/base_rules.mk:325: error: device/leeco/msm8996-common/gps/utils: [email protected] already defined by device/asus/X01AD/libhidl.

buildserv2: Failed build for YTX703F branch: lineage-18.1

[ 21% 186/847] including out/soong/Android-lineage_YTX703F.mk ...
FAILED:
In file included from build/make/core/main.mk:437:
In file included from out/soong/Android-lineage_YTX703F.mk:187789:
In file included from build/make/core/soong_cc_prebuilt.mk:49:
build/make/core/base_rules.mk:325: error: device/lenovo/YTX703-common/hardware/libhidl: [email protected] already defined by device/asus/X01AD/libhidl.
07:45:28 ckati failed with: exit status 1

buildserv2: Failed build for YTX703L branch: lineage-18.1

[ 21% 186/847] including out/soong/Android-lineage_YTX703L.mk ...
FAILED:
In file included from build/make/core/main.mk:437:
In file included from out/soong/Android-lineage_YTX703L.mk:187789:
In file included from build/make/core/soong_cc_prebuilt.mk:49:
build/make/core/base_rules.mk:325: error: device/lenovo/YTX703-common/hardware/libhidl: MODULE.TARGET
[email protected] already defined by device/asus/X01AD/libhidl.

buildserv2: Failed build for zl1 branch: lineage-18.1

[ 27% 230/850] including device/leeco/msm8996-common/Android.mk ...
FAILED:
In file included from build/make/core/package.mk:78:
In file included from device/leeco/msm8996-common/Android.mk:31:
In file included from device/leeco/msm8996-common/libhidl/Android.mk:22:
In file included from build/make/core/shared_library.mk:32:
In file included from build/make/core/shared_library_internal.mk:34:
In file included from build/make/core/dynamic_binary.mk:39:
In file included from build/make/core/binary.mk:9:
build/make/core/base_rules.mk:325: error: device/leeco/msm8996-common/gps/utils: [email protected] already defined by device/asus/X01AD/libhidl.

petefoth · 2025-02-06T09:48:33Z

Thu 06 Feb 25

buildserv3: Failed build for enchilada branch: lineage-22.1
buildserv3: Failed build for eqs branch: lineage-22.1
transient repo sync errors - retry

rik-shaw · 2025-02-06T23:27:10Z

@petefoth do you have mail notification of these failures or how are you obtaining them?

petefoth · 2025-02-07T06:33:14Z

do you have mail notification of these failures or how are you obtaining them?

I have Element (the Matrix client I use) configured to generate a notification for keywords failed (for build failures) and 'uploaded' for failures to rsync the build artefacts to the download server

When a failure occurs, I login to the build server and search the device log file (/mnt/persistent/logs/<device-name>/lineage.....log) for FAILED: to find the failure reason

petefoth · 2025-02-07T17:05:27Z

Fri 07 Feb 25

buildserv3: Failed build for gauguin branch: lineage-22.1

[ 99% 189813/189814] Package OTA: out/target/product/gauguin/lineage_gauguin-ota.zip (priority: 3)
FAILED: out/target/product/gauguin/lineage_gauguin-ota.zip out/target/product/gauguin/ota_metadata
/bin/bash -c "PATH=out/host/linux-x86/bin/:system/extras/ext4_utils/:out/host/linux-x86/bin/:\$PATH out/host/linux-x86/bin/ota_from_target_files --verbose --path out/host/linux-x86 --backup=true   -k user-keys/releasekey --output_metadata_path out/target/product/gauguin/ota_metadata out/target/product/gauguin/obj/PACKAGING/target_files_intermediates/lineage_gauguin-target_files out/target/product/gauguin/lineage_gauguin-ota.zip"

buildserv3: Failed build for grus branch: lineage-22.1
buildserv3: Failed build for gta4l branch: lineage-22.1
buildserv3: Failed build for gta4lwifi branch: lineage-22.1
buildserv3: Failed build for gta4xl branch: lineage-22.1

2025-02-07 22:07:01 - common.py - INFO    : zip2zip.go:103: write /srv/src/LINEAGE_22_1/out/soong/.temp/tmppa0c8uwg: no space left on device

removed all the zips (they should all be on the download server) which caused gta4xlwifi to fail on copying to zips directory - it wasn't there

>> [Sat Feb  8 08:22:18 UTC 2025] Moving build artifacts for gta4xlwifi to '/srv/zips/gta4xlwifi'
'system/build.prop' -> '/srv/zips/gta4xlwifi/lineage-22.1-20250208-microG-gta4xlwifi.zip.prop'
cp: cannot create regular file '/srv/zips/gta4xlwifi/lineage-22.1-20250208-microG-gta4xlwifi.zip.prop': No such file or directory

which killed the docker run: restart 22.1 devices from gauguin - that worked, all built successfully, build run continuing

petefoth · 2025-02-09T07:24:45Z

Sun 09 Feb 25
buildserv2: Failed build for NB1 branch: lineage-21.0

[ 99% 179990/181353] //system/sepolicy:sepolicy_test generate sepolicy_test (priority: 11)
FAILED: out/soong/.intermediates/system/sepolicy/sepolicy_test/79ee1e9077a85cf0a7efae415df2b097/gen/sepolicy_test
out/host/linux-x86/bin/sbox --sandbox-path out/soong/.temp --output-dir out/soong/.intermediates/system/sepolicy/sepolicy_test/79ee1e9077a85cf0a7efae415df2b097/gen --manifest out/soong/.intermediates/system/sepolicy/sepolicy_test/79ee1e9077a85cf0a7efae415df2b097/genrule.sbox.textproto
The failing command was run inside an sbox sandbox in temporary directory
out/soong/.temp/sbox/160d2120b3a2f41a5c5139f683cc3c8e295e8d02
The failing command line can be found in
out/soong/.temp/sbox/160d2120b3a2f41a5c5139f683cc3c8e295e8d02/sbox_command.0.bash
The following types on /data/ must be associated with the "core_data_file_type" attribute.
Violator types and corresponding paths:
('gx_fpd_data_file', '/data/system/fingerprint(/.*)?')

exit status 1

Mon 10 Feb 25

buildserv3: Failed build for heart branch: lineage-22.1

[ 99% 218/219] finishing legacy Make module parsing ...
FAILED:
build/make/core/main.mk:1101: warning:  device/lenovo/heart/lineage_heart.mk includes non-existent modules in PRODUCT_PACKAGES
Offending entries:
libOmxAacEnc
libOmxAmrEnc
libOmxEvrcEnc
libOmxG711Enc
libOmxQcelp13Enc
build/make/core/main.mk:1101: error: Build failed.

buildserv2: Failed build for quill, quill_tab branch: lineage-21.0 - known issue Raise upstream issue about quill & quill_pad recovery image size #706

petefoth mentioned this issue Feb 8, 2025

microg-build3 how to handle zips after they have been synced to download server? #743

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

February 25 Build Run Status #739

February 25 Build Run Status #739

petefoth commented Jan 31, 2025 •

edited

Loading

petefoth commented Feb 2, 2025 •

edited

Loading

petefoth commented Feb 5, 2025 •

edited

Loading

petefoth commented Feb 6, 2025

rik-shaw commented Feb 6, 2025

petefoth commented Feb 7, 2025 •

edited

Loading

petefoth commented Feb 7, 2025 •

edited

Loading

petefoth commented Feb 9, 2025 •

edited

Loading

February 25 Build Run Status #739

February 25 Build Run Status #739

Comments

petefoth commented Jan 31, 2025 • edited Loading

petefoth commented Feb 2, 2025 • edited Loading

petefoth commented Feb 5, 2025 • edited Loading

petefoth commented Feb 6, 2025

rik-shaw commented Feb 6, 2025

petefoth commented Feb 7, 2025 • edited Loading

petefoth commented Feb 7, 2025 • edited Loading

petefoth commented Feb 9, 2025 • edited Loading

petefoth commented Jan 31, 2025 •

edited

Loading

petefoth commented Feb 2, 2025 •

edited

Loading

petefoth commented Feb 5, 2025 •

edited

Loading

petefoth commented Feb 7, 2025 •

edited

Loading

petefoth commented Feb 7, 2025 •

edited

Loading

petefoth commented Feb 9, 2025 •

edited

Loading