10 Jun 2020 |
glennmen | Ok will look into that, honestly I have never written a test for an Android application before 😅 | 09:11:38 |
_hc | this should be as easy as it gets, the whole framework is there | 09:31:06 |
_hc | glennmen: like create app/src/test/java/org/fdroid/fdroid/data/AppTest.java and stick it in there | 09:31:49 |
uniq | I've finally managed to bootstrap vagrant buster basebox images. Builds are available on fdroid/basebox-buster64. Or can be self-built using our basebox script. | 09:44:12 |
_hc | 🎉 | 09:49:05 |
jochensp | uniq: awesome! | 11:22:23 |
Bubu | _hc: uniq I'm thinking the best way forward for the ndk is not provisioning any of them into the buildserver but making the install zips available on a mounted ro partition. | 12:15:12 |
Bubu | I have extarcting them automatically working (and downloading if they're not available) | 12:15:38 |
Bubu | I'm unsure of how the mounted dir works regarding libvirt vs virtualbox | 12:16:11 |
_hc | yes, I completely agree | 12:16:09 |
_hc | they both work | 12:16:36 |
Bubu | We should probably do the same with all gradle installs | 12:17:05 |
_hc | they should mount in the same path | 12:16:57 |
Bubu | it pretty much works the same way | 12:17:12 |
_hc | Bubu: in that scanner crahs, how can I reproduce? I ran fdroid scanner org.telegram.messenger | 12:17:41 |
_hc | but no luck | 12:17:49 |
Bubu | I ran fdroid build -v -l org.telegram.messenger | 12:18:11 |
_hc | Bubu: doesn't gradlew-fdroid already download and verify the gradle binaries? I suppose it could check the buildserver cache before trying to download | 12:21:06 |
_hc | that's been working on the issuebot/fdroiddata CI builds | 12:21:16 |
Bubu | In reply to @eighthave:matrix.org Bubu: doesn't gradlew-fdroid already download and verify the gradle binaries? I suppose it could check the buildserver cache before trying to download it does but we still install most versions into the buildserver by default | 12:21:52 |
Bubu | instead of doing that we could just have the install zips available | 12:22:05 |
_hc | right | 12:22:09 |
_hc | yeah, totally. so gradlew-fdroid would get the gradle version, then check the cache otherwise download, then verify | 12:22:46 |
_hc | that would work quite nicely | 12:22:57 |
_hc | means new gradle versions only need a new gradlew-fdroid version, not a new buildserver rebuild | 12:23:15 |
Bubu | well, we have that already | 12:23:35 |
Bubu | but it's not really used | 12:23:42 |
_hc | it is now used in fdroiddata ci builds :) | 12:27:09 |
Bubu | yes, on the buildserver I meant | 12:29:11 |
_hc | Bubu: I can't reproduce your crash still. That file exists for me:
$ ls -l build/org.telegram.messenger/TMessagesProj/src/main/assets/fonts/rmono.ttf
-rwxr-xr-x 1 hans hans 114624 Jun 10 14:20 build/org.telegram.messenger/TMessagesProj/src/main/assets/fonts/rmono.ttf
| 13:20:12 |