ikarso has quit [Quit: Connection closed for inactivity]
clamor has quit [Read error: Connection reset by peer]
mtoy has quit [Ping timeout: 240 seconds]
mtoy has joined #u-boot
mmu_man has quit [Ping timeout: 265 seconds]
mmu_man has joined #u-boot
naoki has joined #u-boot
mmu_man has quit [Ping timeout: 268 seconds]
alpernebbi has quit [Ping timeout: 248 seconds]
alpernebbi has joined #u-boot
wooosaiiii1 has joined #u-boot
wooosaiiii has quit [Ping timeout: 252 seconds]
wooosaiiii1 is now known as wooosaiiii
clamor has joined #u-boot
gsz has joined #u-boot
alperak has joined #u-boot
monstr has joined #u-boot
monstr has quit [Ping timeout: 252 seconds]
goliath has joined #u-boot
rvalue has quit [Read error: Connection reset by peer]
rvalue has joined #u-boot
mckoan|away is now known as mckoan
gsz has quit [Quit: leaving]
warpme has joined #u-boot
ldevulder has joined #u-boot
clamor has quit [Ping timeout: 272 seconds]
clamor has joined #u-boot
monstr has joined #u-boot
ikarso has joined #u-boot
prabhakalad has quit [Ping timeout: 276 seconds]
prabhakalad has joined #u-boot
javierm has joined #u-boot
sszy has joined #u-boot
Poltawer has joined #u-boot
eballetbo has joined #u-boot
Guest9 has joined #u-boot
prabhakalad has quit [Quit: Konversation terminated!]
Guest9 has quit [Quit: Client closed]
<javierm>
hello, how test/py/tests/test_efi_selftest.py works? If if I try to run it with `pytest --bd sandbox test/py/tests/test_efi_selftest.py`, all the tests are skipped
<javierm>
I can run the bootefi self tests though when booting u-boot and executing from the prompt: bootefi selftest
<javierm>
apalos, xypron ^
gsz has joined #u-boot
rvalue- has joined #u-boot
rvalue has quit [Ping timeout: 260 seconds]
<xypron>
javierm: The sandbox does not enable EFI selftests (CMD_BOOTEFI_SELFTEST).
<xypron>
You could patch configs/sandbox_defconfig
<javierm>
xypron: thanks, that makes sense
rvalue- is now known as rvalue
<derRichard>
Tartarus: i have now a more or less working host mtd driver for u-boot sandbox which extends the host uclass. so far it is less messy than expected.
<derRichard>
so, expect RFC patches :-)
mmu_man has joined #u-boot
Poltawer has quit [Quit: WeeChat 4.6.3]
Poltawer has joined #u-boot
naoki has quit [Quit: naoki]
prabhakalad has joined #u-boot
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<marex>
when I get this "27 1 96%" kind of error report from CI, it is not really useful for debugging this issue , and I still don't know how to perform the same check locally and get more useful info
Poltawer has quit [Quit: WeeChat 4.6.3]
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
warpme has joined #u-boot
<Tartarus>
derRichard: great thanks
<Tartarus>
marex: I think doc/develop/binman_tests.rst covers how to run the tests locally
<Tartarus>
But in turn what python coverage wants, I cannot say, and I can only assume some general searching might help explain how to get a more verbose complaint from some linter
goliath has quit [Quit: SIGSEGV]
<marex>
Tartarus: OK, I give up on binman ... it seems every time I touch that tool, there is a problem like this, it is not improving, and frankly, if even basic debugging of 40 lines or so of code is so complicated with binman, then something is very wrong
<Tartarus>
Well, did you run the python through a linter?
<Tartarus>
I assume it's complaining about a lack of, or not formatted as it wants them, comments
ldevulder has quit [Quit: Leaving]
<marex>
Tartarus: what kind of linter ?
<marex>
Tartarus: maybe the CI should do that ?
mmu_man has quit [Ping timeout: 244 seconds]
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
mmu_man has joined #u-boot
monstr has quit [Ping timeout: 252 seconds]
monstr has joined #u-boot
clamor has quit [Ping timeout: 252 seconds]
clamor has joined #u-boot
vfazio__ has quit [Remote host closed the connection]
vfazio has joined #u-boot
<Tartarus>
It's running the linter which is failing, yes
<Tartarus>
pretty sure that's just running normal python coverage
dsimic has quit [Ping timeout: 268 seconds]
dsimic has joined #u-boot
<marex>
Tartarus: and I am pretty sure you do know the command I am looking for ?
mckoan is now known as mckoan|away
<Tartarus>
Only from looking at the binman_test rst
<Tartarus>
which is binman test -T
<Tartarus>
But if that needs other setup before it just blows up, I assume it's also in that doc
<Tartarus>
It looks like it even talks about how to get more information out and how to figure out wtf to do about it
<marex>
Tartarus: ah sigh ... which leads to the usual cryptic splat from binman, which complains about tools/binman/__init__.py and others code coverage ... sigh
<marex>
I really wonder why this cannot be as simple as checkpatch for example
<Tartarus>
It's python and not C and yes one of my problems is trying to get our python stuff handled via normal tooling and testing paths and not something ad-hoc and home grown
<javierm>
xypron: lib/efi_selftest/efi_selftest_tcg2.c fails with sandbox, I guess is expected given that EFI selftests is not enabled in the sandbox_defconfig
<apalos>
javierm: what fails?
<apalos>
sanbod does provide a software tpm, but it's quite limited iirc
<apalos>
So some of the TCG commands don't work unless we extend that 'sandbox tpm'
<apalos>
But personally I dont see the point. TPMs are pretty complex we can emulate then adequately in QEMU
<javierm>
yeah, I looked at ./drivers/tpm/tpm*_tis_sandbox.c and noticed that
<javierm>
apalos: so what's the correct way to run the EFI selftests then? Not using the sandbox (i.e: pytest --bd sandbox test/py/tests/test_efi_selftest.py --build)
<xypron>
javierm: The tests currently run on the QEMU platforms. Just enter `bootefi selftest`.
<javierm>
xypron: yup, I mentioned that I was testing that. But this part doesn't exercise the test/py/tests/test_efi_selftest.py part
<javierm>
or maybe that's not a problem and I don't really need to hook my new test there ?
<xypron>
javierm: The tcg2 test fails on the sandbox because the sandbox' emulation of a TPM is incomplete. So more changes than only the defconfig would be needed.
<javierm>
xypron: that was my understanding from looking at the code and apalos' comment. I'll just ignore that failing test then
mmu_man has quit [Ping timeout: 248 seconds]
<apalos>
xypron: regarding when to install the new protocol
<apalos>
I am fine having it unconditionally
<apalos>
Installing it with a Kconfig option is 2x the code. The EFI spec doesnt *require* it, but it's small I think it's ok
mmu_man has joined #u-boot
vagrantc has joined #u-boot
teknix has left #u-boot [#u-boot]
tlwoerner has quit [Ping timeout: 248 seconds]
tlwoerner has joined #u-boot
Poltawer has joined #u-boot
gsz has quit [Ping timeout: 248 seconds]
clamor has quit [Read error: Connection reset by peer]
monstr has quit [Remote host closed the connection]