2023-07-09.log

+ jacobk (~quassel@47-186-122-163.dlls.tx.frontiernet.net)00:30
- mjw (QUIT: Ping timeout: 246 seconds) (~mjw@gnu.wildebeest.org)01:09
- jomo (QUIT: Server closed connection) (~jomo@user/jomo)01:20
+ jomo (~jomo@user/jomo)01:20
minuteBoostisbetter: etnaviv is the gpu, not the display engine. the gpu doesn't know anything about the display(s). are you using single or dual display mode?01:24
- murph[m] (QUIT: Server closed connection) (~murphhope@2001:470:69fc:105::d564)01:57
+ murph[m] (~murphhope@2001:470:69fc:105::d564)01:58
- mtm (QUIT: Ping timeout: 245 seconds) (~mtm@c-71-228-84-213.hsd1.fl.comcast.net)02:03
- nsc (QUIT: Ping timeout: 246 seconds) (~nicolas@195-48-142-46.pool.kielnet.net)03:12
+ nsc (~nicolas@228-49-142-46.pool.kielnet.net)03:14
+ bkeys (~Thunderbi@static-198-54-130-101.cust.tzulo.com)03:35
+ mtm (~mtm@c-71-228-84-213.hsd1.fl.comcast.net)04:09
- anzu (QUIT: Server closed connection) (~anzu@melkki.cs.helsinki.fi)05:17
+ anzu (~anzu@melkki.cs.helsinki.fi)05:17
- ex-parrot (QUIT: Server closed connection) (~fincham@user/ex-parrot)05:38
+ ex-parrot (~fincham@user/ex-parrot)05:39
- lifning (QUIT: Server closed connection) (~lifning@user/lifning)05:47
+ lifning (~lifning@user/lifning)05:47
- vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:50)05:59
joschwould anybody like to be my guinea pig for the reform.debian.net stable apt repo?06:34
- robin (QUIT: Ping timeout: 246 seconds) (~robin@user/terpri)06:35
joschif yes, follow these steps: https://reform.debian.net/06:35
ex-parrotkeen06:44
ex-parrotmy reform is apart at the moment but I can set this up06:45
ex-parrotexciting06:45
ex-parrotI was going to try get an out-of-the-box Bookworm going06:45
ex-parrotonce I have it back together06:45
Boostisbetterminute: I would think single as I have never changed it. 07:10
- Boostisbetter (QUIT: Ping timeout: 240 seconds) (4a410829d7@irc.cheogram.com)08:14
+ Boostisbetter (4a410829d7@irc.cheogram.com)08:21
- qbit (QUIT: Quit: WeeChat 3.8) (~qbit@2602:ff16:3:0:1:3a0:0:1)09:22
+ robin (~robin@user/terpri)09:32
+ robin_ (~robin@user/terpri)09:39
- robin (QUIT: Ping timeout: 246 seconds) (~robin@user/terpri)09:39
ex-parrotgoing to try and safely remove the serial number sticker from my damaged base plate...10:03
ex-parrotOk I warmed it up, peeled it off and stuck it on some adhesive laminating film to make it in to a tag. Now I’ll just secure that inside the chassis for all eternity. 10:13
ex-parrothttps://img.hotplate.co.nz/K7Joe9YMuu10:13
joschi still haven't put my sticker XD10:15
ex-parrotI'm not sure I recommend putting it on the outside of the bottom lid :P10:15
ex-parrotnow I have a new lid I can do some Science on the old lid and see if the cracks would have been fixable by injecting resin10:17
- deflated8837 (QUIT: Server closed connection) (~deflated8@50.53.206.61)10:27
+ deflated8837 (~deflated8@50.53.206.61)10:27
ex-parrotthe cracks have continued spreading in the old lid so it definitely needed something done 10:33
- klardotsh (QUIT: Ping timeout: 246 seconds) (~klardotsh@98.97.115.75)11:02
+ eery (~eery@77.137.76.80)11:23
joschuff number #000037 -- that's impressive! :D11:24
+ Booster[m] (~boosterbo@2001:470:69fc:105::3:3d99)11:45
+ mjw (~mjw@gnu.wildebeest.org)13:15
minutejosch: exciting @ debian reform repo13:32
minutei'm currently travelling to paris for FSiC2023 and only have my pocket reform with me13:32
joschthat's also exciting!13:34
joschi started my switch to 100% reform also with a trip -- portugal to my partner's family for 3 weeks and all i had with me wath the reform and a screwdriver :)13:35
joschi was running kde plasma on the reform back then13:35
joschminute: i also have the hdmi situation fixed -- was there anything else that needed to be taken care of?13:35
joschc-keen[m], violet: i think i have fixed the hdmi situation but i cannot do a final test because i do not have a hdmi monitor -- would either or both of you like to test the fixed kernel?13:41
- eery (QUIT: Remote host closed the connection) (~eery@77.137.76.80)13:57
- grubaroni (PART: !!unknown attribute: msg!!) (~user@user/grubaroni)13:58
minutejosch: oh great, thanks a ton for fixing it. i will test it after coming back on tuesday14:01
minuteyesterday i improvised and watched a movie with my partner using pocket's hdmi and usb audio14:01
- mtm (QUIT: Ping timeout: 250 seconds) (~mtm@c-71-228-84-213.hsd1.fl.comcast.net)14:03
joschi just canceled a scheduled run of reform-debian-packages because it would've run a job in the middle of another pipeline i had running for the cdns-fix branch -- breaking both pipelines as a result14:20
joschi then looked for a way to force gitlab to only start jobs from a new pipeline *after* all older pipelines are done14:21
joschit seems there is an API call that allows setting process_mode to oldest_first that achieves exactly that: https://stackoverflow.com/a/74883391/78466914:21
joschcurl --request PUT --data "process_mode=oldest_first" --header "PRIVATE-TOKEN: <your_access_token>" "https://gitlab.example.com/api/v4/projects/1/resource_groups/production"14:24
joschminute: is this something you can look into next week?14:24
- Boostisbetter (QUIT: Ping timeout: 260 seconds) (4a410829d7@irc.cheogram.com)14:38
minutejosch: my flight is delayed so i can click around in the web interface in a few minutes (or adjust settings via ssh on the build server)14:50
+ Boostisbetter (4a410829d7@irc.cheogram.com)14:53
joschhere is the gitlab upstream issue: https://gitlab.com/gitlab-org/gitlab/-/issues/1654815:05
minutejosch: you have root acccess to the builder, right? could you add this key to authorized_keys? http://dump.mntmn.com/id_rsa_reform.pub.txt15:10
minute(realized that my account on my pocket is not yet authorized on that server)15:11
joschminute: hrm... i'm not sure it's very responsible to give somebody ssh access if i cannot be sure whether the account named "minute" here is really Lukas or not -- do you have a gpg key that you can sign your message with?15:13
minutejosch: ah, i thought my ownership of the domain might be enough :315:14
minutei can also put it on mntre.com15:14
minutei also don't have my gpg private key with me :315:15
minutei think i can also gain control over the server by using the remote console, lets see15:16
joschminute: true -- unlikely that anybody else wan do this15:16
joschone sec15:16
joschminute: done15:16
joschdoes it work?15:16
minutethanks, one moment15:17
minuteah, i realize i am also not opped here15:17
* ChanServ changed mode (+o, minute)15:17
minutejosch: hmm, ssh access doesn't work for me. not sure what's wrong15:18
minute(i.e. it's asking for a pw)15:19
minutejosch: you added me to root@ ?15:19
joschthe username is mntmn15:19
minuteoh15:19
Boostisbettera password on the cert right?15:19
joschno, to /home/mntmn/.ssh/authorized_keys15:19
minutejosch: alright, thanks15:19
minuteworks15:19
joschnice! :)15:19
minutei also have the sudo pw with me for some reason, so i have root access, thanks15:20
+ qbit (~qbit@h.suah.dev)15:20
minuteok so the runner has builds_dir = "/ramdisk/builds"15:21
minuteand executor is docker15:21
minutejosch: not sure i understand how different build's data should affect each other 15:21
minutedo we need to disable the cache?15:21
minutedisable_cache = false15:22
joschminute: i explained the problem here yesterday15:22
joschessenitally the problem is the shared build space15:22
minuteok, but why would it not create a different subdirectory for each build15:22
minuteactually there is no /ramdisk/builds15:23
minutethere is only /ramdisk/docker/volumes/15:23
minutethese are called sth like:15:23
joschthe git repository for which the build is done always gets put into /ramdisk/builds/reform/reform-debian-packages15:23
joschbut that is a path from inside the docker image15:23
minutehuuuh15:23
joschthe path outside might be different15:24
minutejosch: well, docker containers can only write to their own temp storage, to their cache and to volumes mounted into the container15:25
minutewe used to run the builds in a shell executor that used a shared /ramdisk/builds, but we don't do that since a longer time anymore15:26
joschlet me write you a small script that demonstrates the behaviour15:26
minuteok15:26
joschminute: consider this .gitlab.yml: https://source.mnt.re/reform/reform-debian-packages/-/blob/cidemo/.gitlab-ci.yml?ref_type=heads15:30
minutejosch: yep15:31
minuteif "demo exists", i would consider that a bug15:31
joschminute: in the first pipeline run, the file "demo" doesn't exist: https://source.mnt.re/reform/reform-debian-packages/-/jobs/149915:31
joschin the second pipeline run it exists: https://source.mnt.re/reform/reform-debian-packages/-/jobs/150015:31
minutewtf15:32
minutethis should def. not happen!15:32
joschso state is shared between multiple pipelines15:32
joschi agree15:32
minutenot sure why this happens15:32
joschme neither -- i have little to no clue about gitlab unfortunately15:32
joschi just see the effects15:33
minutei just took away the old "builds_dir" setting, maybe that caused this... can you rerun your test pipeline?15:35
joschminute: maybe that was it! https://source.mnt.re/reform/reform-debian-packages/-/jobs/150115:36
minutejosch: did you run it twice already?15:37
joschyes15:37
joschthis is the third time15:37
joschor did you clean it up before?15:37
joschlet me run it a fourth15:37
minutegreat. i did not do any manual cleaning15:38
minutebut i did restart the runner after removing that setting15:38
joschit exists :( https://source.mnt.re/reform/reform-debian-packages/-/jobs/150215:38
joschso restarting the runner resets the state15:38
minutecrap15:39
minutewhy would it behave like that....15:39
minutejosch: normally only /cache should be persistent15:40
joschi'm sorry i cannot be of more help and for having unearthed this frustrating issue :(15:42
minutewell it's important to know15:43
minutei just removed more options from the config.toml and restarted15:43
minutei also set cache to disabled15:43
minutecan you try a few more test builds?15:43
joschi'll schedule two more15:43
minutei am also looking at docker ps to see if docker is used at all :D15:44
minute(so far it's quiet, but maybe i'm not seeing the jobs with a watch interval of 1s)15:44
joschshould i put a sleep into the job?15:44
minuteyes please, maybe sleep 2s15:45
minutesleep 215:45
joschpushed15:45
minuteon a positive side, working on remote admin stuff with pocket reform works well :D i just need to work on battery life15:45
minuteah, saw the container!15:46
minuteit popped up briefly in docker ps, so docker is def. used :D15:46
joschnow running a second time15:46
minute779ce52029eb   dc29b27ee12f   "sh -c 'if [ -x /usr…"   1 second ago   Up Less than a second             ru15:46
minutenner-rp9pp3ds-project-67-concurrent-0-184ded908bce0abb-build-215:46
josch++ echo 'demo doesn'\''t exist'15:47
joschaha!15:47
joschthat looks good15:47
minute:015:47
minutei also don't see any leftovers in /ramdisk/docker/volumes15:48
joschthen let me trigger the normal pipeline again to see if that still works15:48
minuteyip15:48
minutewhile the build is running, there is a volume for it:15:49
minuterunner-rp9pp3ds-project-67-concurrent-0-93e000d956e21e8c-cache-c33bcaa1fd2c77edfc3893b41966cea815:49
joschpipeline is running: https://source.mnt.re/reform/reform-debian-packages/-/pipelines/108015:49
joschlets hope that some state survives between the jobs of the same pipeline :D15:49
minutesoo i think what was happening is that the entire build was happening inside a cache volume that was reused?!15:50
minutejosch: ah, do you need to have state survive in the same pipeline?15:50
joschyes, or otherwise splitting the pipeline into multiple jobs isn't doing much15:51
minuteah :D15:54
joschminute: well at least you were very successfully in eliminating shared state :D https://source.mnt.re/reform/reform-debian-packages/-/jobs/150615:54
joschmaybe the right way to do this is to use job artifacts to get the data from one job to the next?15:55
joschi'll have to investigate how that is done15:55
minutejosch: thanks, otherwise lets undo the split perhaps15:55
minuteif it's too complex15:56
minutebut i think taking artifacts from another build is the way to go15:56
joschit seems that how i've done the split was incorrect15:56
joschbecause it only worked because of the (wrong) shared state situation that you fixed15:56
joschand in fact i need to declare artifacts... lets see...15:57
minutelol!15:57
minutewe _can_ share state via volumes but i don't think it would be very clean15:57
joschyes, encoding what is getting passed on this in the .gitlab.yml sounds like a better idea15:58
joschokay, new pipeline is running. I have no idea whether a job can depend on multiple jobs writing into the same directory and whether the contents of that directory are then merged... but i guess we'll see. :)16:04
+ mtm (~mtm@c-71-228-84-213.hsd1.fl.comcast.net)16:08
joschDownloading artifacts from coordinator... ok        id=1510 responseStatus=200 OK token=64_852Ne16:09
joschnice :)16:09
minutenice16:19
minutei think you can make complex pipelines that depend on artifacts built on multiple builders in parallel etc16:20
Boostisbetterminute: the Amiga shot on the website is also great! I can't help but wishing the 8-bit guy would do some brightening on your 3000 though. Do you know I never got to experience the Commodore or Amiga. I was only exposed to the x86 world of the PC. 17:06
BoostisbetterA real shame. 17:06
BoostisbetterIt really makes me wonder how the inferior processing might of those products didn't win out. 17:30
Boostisbetterjust goes to show you how things live or die based on the intensity and quality of their marketing campaigns 17:30
minuteBoostisbetter: not a fan of 8 bit guy18:51
minuteBoostisbetter: commodore and amiga was pretty cool back in the day!18:52
Boostisbetterminute: really? You just don't like his personality, or is it something more serious? I don't like all of his content, but I really like Planet X, and I think the X16 seems interesting as well. 19:12
BoostisbetterI also really appreciated the history series on the Commodore and Amiga products. For someone who never used even one of them, I thought it was very interesting. 19:15
minuteBoostisbetter: i got really turned off the politics, open carry advocacy, stunts with assault rifles in public etc19:23
minuteby the19:25
Boostisbetterminute: I understand. I very much support open carry, not so much stunts with assault rifles in public though. 19:28
minute:S19:29
Boostisbetterdifferences in opinion are one of life's only certainties it seems. I will say that I genuinely wished we lived in a world where all weapons could be destroyed now and forever. 19:30
Boostisbetterbut such talk is inappropriate here I think, so my apologies for bringing it up. 19:31
BoostisbetterMy Reform bricked again today. I need to get the lead out and upgrade my LPC and keyboard firmware. 19:31
BoostisbetterI think tomorrow I am going to book some time in the afternoon, if the heat isn't killing me, to knock it out. 19:32
minutei just arrived at charles de gaulle airport and trying to make my way to paris.19:32
joschstill on the pocket -- nice! :)19:33
Boostisbetterminute: indeed! Being on the pocket is awesome. All the best in Paris. Hope you find some amazing food while you are there!19:44
minuteno, now i am on iphone lol19:45
minutesorry to disappoint19:46
minutei did charge the pocket in the plane though19:46
minutethey had a 60W usb-c outlet19:46
- jacobk (QUIT: Quit: http://quassel-irc.org - Chat comfortably. Anywhere.) (~quassel@47-186-122-163.dlls.tx.frontiernet.net)20:12
Boostisbetternoice!20:43
- deflated8837 (QUIT: Read error: Connection reset by peer) (~deflated8@50.53.206.61)20:46
+ deflated8837 (~deflated8@50.53.206.61)20:49
- bkeys (QUIT: Ping timeout: 246 seconds) (~Thunderbi@static-198-54-130-101.cust.tzulo.com)20:51
+ bkeys (~Thunderbi@static-198-54-130-101.cust.tzulo.com)20:55
joschminute: you based your a311d branch on top of the pocket reform branch which i now cleaned up and rebased on top of the fixed ci branch21:30
joschminute: since pocket reform needs kernel 6.4, would like me to create another branch (i'll not mess up your a311d branch) containing your a311d patches on top of 6.4?21:30
- Gooberpatrol66 (QUIT: Quit: Leaving) (~Gooberpat@user/gooberpatrol66)21:37
- bluerise (QUIT: Ping timeout: 264 seconds) (~bluerise@user/bluerise)22:26
+ bluerise_ (~bluerise@p5b211f1e.dip0.t-ipconnect.de)22:26
+ amospalla (2a2f8bc48e@telesto.hot-chilli.net)22:29
amospallahi, just configured a IRC client besides the webchat.22:33
- buckket (QUIT: Quit: buckket) (~buckket@vps.buckket.org)22:40
+ buckket (~buckket@vps.buckket.org)22:41
ex-parrotmorning22:52
+ vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:50)23:03
pandora[m]<josch> "maybe the right way to do this..." <- It is! That makes things also more reproducible without running everything again :)23:07
joschminute: 23:08
joscherror: arch/arm64/boot/dts/amlogic/meson-g12b-bananapi-cm4-cm4io.dts: already exists in index23:08
joscherror: arch/arm64/boot/dts/amlogic/meson-g12b-bananapi-cm4.dtsi: already exists in index23:08
josch6.4 already seems to include lots of stuff23:08
+ amospalla93 (~amospalla@212.231.228.113)23:15
- amospalla (PART: !!unknown attribute: msg!!) (2a2f8bc48e@telesto.hot-chilli.net)23:15
* amospalla93 -> amospasdfsdfsdf23:16
- amospasdfsdfsdf (QUIT: Client Quit) (~amospalla@212.231.228.113)23:16
+ amospalla18 (~amospalla@212.231.228.113)23:16
- amospalla18 (PART: !!unknown attribute: msg!!) (~amospalla@212.231.228.113)23:16
joschminute: 42 files changed, 70 insertions(+), 3479 deletions(-)23:30
joschminute: so rebase onto 6.4 allows dropping 3.4 thousand lines of patches23:30
+ amospalla (2a2f8bc48e@telesto.hot-chilli.net)23:32
- amospalla (PART: !!unknown attribute: msg!!) (2a2f8bc48e@telesto.hot-chilli.net)23:39
+ amospalla (2a2f8bc48e@telesto.hot-chilli.net)23:40

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!