<sjg1>
apteryx: I see the same thing. I wonder why there is such a bug jump in the series numbering. I can only imagine it is a bug or problem with patchwork. You can get the same error with curl
<apteryx>
I'm not used to patchwork, perhaps that top-right number I can copy when looking at a patch is not what is needed for Series-links: ?
<apteryx>
is there a way to specify, at the git directory level, the project name? that'd be handy for my use case (using patman when working on Guix)
<apteryx>
perhaps it could be stored in the local git config, e.g. 'git config patman.project guix-patches' ?
<apteryx>
git allows that
<sjg1>
apteryx: yes it needs yo be a series number, so maybe sure you are looking at the series view
<apteryx>
if set, that'd take precedence over the current project discovery mechanism, which supports only linux or uboot
<sjg1>
Apteryx yes I'm sure that could be done. Do you know python
<apteryx>
yes! if the design seems OK, I can give it a go
thopiekar_ has quit [Ping timeout: 268 seconds]
thopiekar has joined #u-boot
<sjg1>
Apteryx that seems ok to me
<apteryx>
ok!
PhoenixMage has joined #u-boot
mmu_man has quit [Ping timeout: 260 seconds]
<apteryx>
does ./patman test passes for you on master? ~/src/u-boot/tools/patman [env]$ ./patman test
<apteryx>
-> Ran 44 tests in 7.174s \n\n FAILED (failures=11)
<apteryx>
mostly due to test_checkpatch.py's check_single_message, apparently
PhoenixMage has quit [Ping timeout: 268 seconds]
<apteryx>
OK, this depends on checkpath.pl, so something changed in it and broke the tests
<apteryx>
(my guess)
Leopold has quit [Remote host closed the connection]
Leopold has joined #u-boot
<apteryx>
ah, we now have to invoke the script with '--u-boot'
<apteryx>
down to 1 failure :-)
<apteryx>
oh, the kernel has standardized to use tabs for indentation? we can see that in the changelog of the checkpatch.pl script updated with commit 587254ebcf05fa76b6a957ffa72db053177836cf (u-boot)
mwalle has quit [Quit: WeeChat 3.0]
<marex>
apteryx: are you running aspell on docs ?
<apteryx>
no, I caught these reading it as an info manual in Emacs :-)
<marex>
well either way, nice, thanks
<marex>
btw xypron == Heinrich
<apteryx>
np!
<xypron>
o/
<apteryx>
\o
<marex>
\o/
<marex>
xypron: see you at fosdem again ?
<xypron>
marex: that is planned
<marex>
very good
<marex>
xypron: doing a talk ?
<xypron>
marex: no.
<marex>
xypron: Forty-Bot is likely coming too btw ... so ... who else is coming ?
<marex>
sjg1: ^ ?
<apteryx>
yay, test suite passes
<apteryx>
(patman's test suite)
<marex>
nice
Leopold has quit [Remote host closed the connection]
Leopold has joined #u-boot
<apteryx>
and the test suite can now be run the same via pytest
<apteryx>
perhaps the semi-custom unit tests runner could be dropped and the documentation how to use pytest to run the test suite?
<apteryx>
*documentation update to refer to pytest
<apteryx>
*updated oof.
* apteryx
goes to get some sleep time
<apteryx>
o/
vagrantc has joined #u-boot
<marex>
very nice :)
vagrantc has quit [Quit: leaving]
mckoan_ has joined #u-boot
mckoan|away has quit [Ping timeout: 252 seconds]
sdhsdsj has joined #u-boot
apritzel_ has joined #u-boot
sdhsdsj has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
ebach has joined #u-boot
apteryx has quit [Ping timeout: 272 seconds]
apteryx has joined #u-boot
Leopold has quit [Remote host closed the connection]
rvalue has quit [Read error: Connection reset by peer]
rvalue has joined #u-boot
camus has quit [Remote host closed the connection]
camus has joined #u-boot
apritzel_ has joined #u-boot
Leopold has quit [Remote host closed the connection]
Leopold has joined #u-boot
UncleBen has quit [Quit: salvia]
camus1 has joined #u-boot
camus has quit [Ping timeout: 255 seconds]
camus1 is now known as camus
apritzel_ has quit [Ping timeout: 256 seconds]
sbach has quit [Read error: Connection reset by peer]
sbach has joined #u-boot
Leopold has quit [Quit: No Ping reply in 180 seconds.]
Leopold has joined #u-boot
persmule has quit [Remote host closed the connection]
<sjg1>
marex: No I don't see anything about booting, etc. on the agendas. Did I miss something?
<sjg1>
apteryx: I think having more docs on using pytest to do things is a good idea. Which semi-custom test runners do you mean? The one in test_utils ?
persmule has joined #u-boot
apritzel_ has joined #u-boot
naoki has quit [Quit: naoki]
visibig has joined #u-boot
visibig has quit [Remote host closed the connection]
visibig has joined #u-boot
<visibig>
Hi I have a question do you know if there is a planning to integrate a btrfs rescue like what did in btrfs-utils for example in some cases when a disk corruption occurs on roots we may fix it with btrfs rescue log zero???
<marex>
sjg1: embedded/automotive track and bootloader track, there are two
<marex>
visibig: boot linux with ramdisk, recover from there, that's probably the best option
<visibig>
This solution isn't to be explored for what we use the uboot.
<visibig>
We need
<visibig>
To be automatically recoverable
<visibig>
For example after 3 reboots we launch the rescue strategy
<marex>
you can use bootcounter + watchdog for that , just stick your recovery boot command into altbootcmd
<marex>
maybe I don't understand the question though
<marex>
are you trying to recover the filesystem , or fiddle with volumes in some way ?
<marex>
or just run some other command after a few unsuccessful boots ?
<visibig>
If I understand we have those mechanisms, use the boot counter and a watchdog to reset the device and after that with an other partition we launch a recovery system from an other clean recovery partition ? Altbootcmd stands for alternative boot command????
<visibig>
Thank you for your hints I think I have something to work with to make a workaround
<marex>
yeah, if the system reboots a few times (see bootlimit env variable) without resetting the bootcounter, it starts altbootcmd script instead of bootcmd script
<visibig>
Ok thank you very much
<marex>
this has nothing to do with btrfs though
<marex>
the functionality is generic
prabhakarlad has quit [Ping timeout: 260 seconds]
thopiekar has quit [Ping timeout: 252 seconds]
thopiekar has joined #u-boot
<marex>
the hush shell code ... urgh
camus has quit [Remote host closed the connection]
camus has joined #u-boot
thopiekar has quit [Ping timeout: 246 seconds]
thopiekar has joined #u-boot
redbrain has quit [Read error: Connection reset by peer]
redbrain has joined #u-boot
camus has quit [Remote host closed the connection]
camus has joined #u-boot
* marex
faints from the repugnant encoding of return codes ... ugh
<marex>
now it starts to make sense what this return -rcode - 2 is all about , and how -2 is special error code indicating exit ... yuck