| 16 Nov 2024 |
atemu12 | Huh okay | 00:07:21 |
atemu12 | Good do know | 00:07:37 |
oak 🏳️🌈♥️ | I think it could be a good idea to put some maximum in that default if it's based in CPU core count | 00:13:28 |
atemu12 | I think repo does that by default | 00:13:48 |
oak 🏳️🌈♥️ | https://github.com/nix-community/robotnix/blob/master/scripts/mk_repo_file.py#L251 | 00:15:32 |
oak 🏳️🌈♥️ | It's not like the git cloning problem is that much CPU bound anyway, the most speedup comes from if some jobs wait for remote doing something while others can transfer during that time | 00:16:58 |
atemu12 | You'd be surprised how CPU-bound it can be | 00:18:27 |
atemu12 | Git needs to undo the delta compression for a whole bunch of BLOB repos and kernels | 00:19:01 |
atemu12 | When I run the updater on my little home 4C server, it readily maxes out the CPU | 00:19:58 |
oak 🏳️🌈♥️ | Now it's time to test, lineage-19.1 build | 00:33:35 |
oak 🏳️🌈♥️ | * Now it's time to test, lineage-19.1 build (without webview) | 00:33:46 |
oak 🏳️🌈♥️ | I wonder if I should create issues for all the things I encounter | 00:35:47 |
atemu12 | Depends on what they are | 00:36:16 |
atemu12 | There's a matrix for stuff that's expected to work or not | 00:36:27 |
oak 🏳️🌈♥️ | It wasn't actually the webview that was failing, I think it was the chromium apk package itself | 00:37:00 |
atemu12 | Yeah that's not unexpected | 00:37:17 |
atemu12 | I created an issue on yeeting chromium earlier | 00:37:31 |
oak 🏳️🌈♥️ | Ah yes this one I did encounter before:
error: hash mismatch in fixed-output derivation '/nix/store/hcz1f4ld47syakxfkl54p6s3g3jr972i-android_external_chromium-webview_prebuilt_arm-3a32a73.drv':
specified: sha256-XEzHw0c/xPM3X8VDptJNZln2aOlxhkRXp+EDp1eM4NI=
got: sha256-C9Syc7A5OyL4iGV1n9qNvwsZ//A5t3E5PDOR0wd5Mu8=
For all these webview prebuilts the hashes are wrong, these should get updated by the update.sh?
| 00:39:13 |
atemu12 | Nope, webview stuff is entirely separate | 00:39:39 |
atemu12 | update.sh is for lineageos onlu | 00:39:45 |
atemu12 | * update.sh is for lineageos only | 00:39:49 |
oak 🏳️🌈♥️ | Yeah and if I fix the hashes manually inside the lineage-19.1/repo.json then they start to work | 00:40:31 |
oak 🏳️🌈♥️ | I realized I actually need to set the webview setting to false because it probably defaults to true | 00:44:45 |
oak 🏳️🌈♥️ | * I realized I actually need to set the webview setting to false (in my configuration) because it probably defaults to true | 00:45:03 |
oak 🏳️🌈♥️ | Okay now it actually tried to build and:
FAILED: out/target/product/instantnoodlep/obj/ETC/build-manifest_intermediates/build-manifest.xml
/bin/bash -c "(mkdir -p out/target/product/instantnoodlep/obj/ETC/build-manifest_intermediates/ ) && (python3 .repo/repo/repo manifest -o - -r | grep -Ev \"proprietary_\" > out/target/product/instantnoodlep/obj/ETC/build-manifest_intermediates/build-manifest.xml )"
python3: can't open file '/build/.repo/repo/repo': [Errno 2] No such file or directory
| 00:58:11 |
oak 🏳️🌈♥️ | Well I'll simply try to go to back to that commit id you gave | 01:06:39 |
atemu12 | It appears to be attempting to run repo during the build? | 01:07:23 |
atemu12 | That suggests to me it's missing some source dir | 01:07:32 |
oak 🏳️🌈♥️ | I'm guessing it's trying to run repo to generate some kind of manifest to be included in the build | 01:16:02 |
atemu12 | Ah if you look closer it appears to be missing the proprietary vendor stuff | 01:16:45 |