<chroot_0x01>
Can some please explain, what form of email address following this "If you are registering an account, please send a short e-mail to source-admins AT denx DOT de with your username afterwards." should have? Please add an example, if the username is not meant to be sent within 'subject' line.
<marex>
what are you trying to do ?
alexxy has joined #u-boot
<Tartarus>
Sign up with our gitlab
<Tartarus>
And yes, email that address and ask for your account to be activated. It's read by a human, not an automated system
chroot_0x01 has quit [Ping timeout: 256 seconds]
persmule has quit [Remote host closed the connection]
<xypron>
sjg1: buildman's select_boards() describes excludes is a list of str but we are using exclude.matches() which only exists for regular expressions. So it seems that exclude is a list of str defining regular expressions. E.g. '^malta' could be used to exclude all malta* boards? I think we need some more precision in the documentation of buildman.
Stat_headcrabbed has quit [Quit: Stat_headcrabbed]
<xypron>
sjg1: I was looking at the Python code. In the html doc there is an example with a regular expression, ok.
<xypron>
and regular expression is mentioned
<sjg1>
Tartarus: I got an arm64 machine and it sort-of passes CI tests. I have no idea how it could be connected to gitlab though. The docker image has some parts which assume x86_64, from what I can tell
<xypron>
sjg1: We need a new Docker image and a new Dockerfile.
<xypron>
sjg1: Just add Dockerfile.arm64 in the same directory.
<Tartarus>
We need to re-work the Dockerfile to a proper multi-arch format, yeah
<xypron>
Tartarus: Chat-GPT suggests this if you want a single Dockerfile for multiple architectures: https://paste.ubuntu.com/p/mXWg5Pdc6F/ and then pass the environment argument as --build-arg ARCH=arm64 to buildx.
<xypron>
Would you prefer a single Dockerfile?
<Tartarus>
I have zero faith in chatgpt/et al
<Tartarus>
So please let me know when you've got something tested and working.
<Tartarus>
And whichever way you think looks clean and maintainable long term
jfsimon1981_b has quit [Read error: Connection reset by peer]
jfsimon1981 has joined #u-boot
LainExperiments has joined #u-boot
slobodan_ has joined #u-boot
slobodan has quit [Ping timeout: 252 seconds]
mmu_man has quit [Ping timeout: 264 seconds]
mmu_man has joined #u-boot
slobodan_ is now known as slobodan
LainExperiments has quit [Quit: Client closed]
jclsn has quit [Quit: WeeChat 4.4.2]
jclsn has joined #u-boot
<sjg1>
Tartarus: xypron: OK. I have no idea what I am doing but I will see if I can send a patch to start things off
<sjg1>
But another problem is how to use it with gitlab
mmu_man has quit [Ping timeout: 265 seconds]
<xypron>
sjg1: You can assign tags to jobs in .gitlab.yaml. Then Gitlab will look for runners matching the tags. E.g. you could have a single job for sandbox on arm64 and only this job for each pipeline would run on your arm machine. All others remain on x86.
mmu_man has joined #u-boot
jclsn has quit [Quit: WeeChat 4.4.3]
<sjg1>
xypron: Yes that sounds like a good idea. That's what I did for my hardware lab
naoki has joined #u-boot
jclsn has joined #u-boot
jclsn has quit [Client Quit]
slobodan has quit [Ping timeout: 260 seconds]
naoki has quit [Quit: naoki]
naoki has joined #u-boot
prabhakalad has quit [Quit: Konversation terminated!]
prabhakalad has joined #u-boot
jclsn has joined #u-boot
mmu_man has quit [Ping timeout: 252 seconds]
mmu_man has joined #u-boot
goliath has quit [Quit: SIGSEGV]
fatal has quit [Remote host closed the connection]