<vmeson>
thanks khem. if you have any info on build time delta and runtime improvements that would be appreciated but I expect that you don't and I should test it myself.
sotaoverride is now known as Guest3427
Guest3427 has quit [Killed (silver.libera.chat (Nickname regained by services))]
sotaover1ide is now known as sotaoverride
florian has quit [Ping timeout: 276 seconds]
ctraven has joined #yocto
Kubu_work has quit [Quit: Leaving.]
<khem>
With mold ? No I don’t have any numbers I think lld is good enough for linking needs as of now for what I deal with
qschulz has quit [Quit: qschulz]
qschulz has joined #yocto
jpuhlman has joined #yocto
prabhakarlad has quit [Quit: Client closed]
davidinux has quit [Ping timeout: 252 seconds]
davidinux has joined #yocto
amitk has joined #yocto
amitk has quit [Ping timeout: 252 seconds]
jclsn has quit [Ping timeout: 246 seconds]
jclsn has joined #yocto
Minvera has quit [Ping timeout: 256 seconds]
lthadeus has joined #yocto
<khem>
RP: btw. I am seeing that ptest when run in parallel fail randomly and the reason when it fails is that ssh to target does not succeed and I see this kernel crash in qemu always - https://snips.sh/f/sjfzUuXZt9
<khem>
RP: I think its definitely related because ssh times out in this case and test fails but in other runs it passes ok and the crash is not seen
<nico39>
Thanks rburton! exactly what I was looking for
<rburton>
its not pretty ;) (I'm allowed to say that as I wrote a lot of it)
Guest456123 has joined #yocto
gsalazar_ has quit [Ping timeout: 256 seconds]
<Guest456123>
Hi,
<Guest456123>
How can we disable a particular toolchain's oe-selftest in poky? Is there any option/file to disable a particular toolchain oe-selftest while all other oe-selftests continue to run?
<Guest456123>
There's a option "PACKAGECONFIG" which can be used to enable/disable some features. Can we disable using that?
<rburton>
Guest456123: can you be more precise about what test you actually mean?
neofutur_ has quit [Ping timeout: 240 seconds]
neofutur has joined #yocto
<Guest456123>
For eg. if I can skip or disable gcc oe-selftest when the following command is given to test all test suites
<Guest456123>
oe-selftest -a
<Guest456123>
I know there is a "--skip-tests" option to skip them while giving the command.
<Guest456123>
But, can this be done using some variable/task in .bb file??
olani- has quit [Ping timeout: 264 seconds]
Mike23 has joined #yocto
lthadeus has quit [Remote host closed the connection]
<rburton>
Guest456123: no, not from a recipe, unless you want to go and start deleting test cases. just use --exclude-tag and filter out all the toolchain tests, or --skip-tests if you want to be very precise
<Guest456123>
If not recipe file, is there any other way?
<rburton>
you tell selftests to skip certain tests
<rburton>
you want to skip tests when running oe-selftest. oe-selftest has several ways of skipping tests.
<Guest456123>
I want to skip the complete test suite (present under meta/lib/oeqa/selftest/cases/*.py file, example- gcc.py) rather than individual test cases when running "oe-selftest -a"
<rburton>
just the gcc tests, or all toolchain tests (such as glibc too)
<Guest456123>
yeah, just gcc (only 1 toolchain)
<rburton>
--skip-tests gcc works, afaik
<rburton>
that will still run the entire glibc test suite
<Guest456123>
So, no other way apart from "--skip-tests"?
<rburton>
correct
<Guest456123>
Ok, thanks rburton
amitk_ has joined #yocto
<rburton>
a bbappend would manipulate the _recipe_ but that isn't the _test case_
amitk has quit [Ping timeout: 255 seconds]
Guest91 has joined #yocto
Guest91 has quit [Client Quit]
Mike23 has quit [Quit: Client closed]
florian_kc has joined #yocto
olani- has joined #yocto
vladest has quit [Remote host closed the connection]
vladest has joined #yocto
Guest456123 has quit [Ping timeout: 250 seconds]
rob_w has quit [Ping timeout: 264 seconds]
neofutur has quit [Ping timeout: 276 seconds]
neofutur_ has joined #yocto
rob_w has joined #yocto
gsalazar_ has joined #yocto
rob_w has quit [Remote host closed the connection]
Dartmoness has joined #yocto
gsalazar_ has quit [Ping timeout: 268 seconds]
<RP>
khem: I think I do understand that bug, I think it is the qemu logging issue we've talked about on the mailing list. Linaro were working on a patch
Kubu_work has quit [Ping timeout: 264 seconds]
zpfvo has quit [Ping timeout: 256 seconds]
zpfvo has joined #yocto
Kubu_work has joined #yocto
zpfvo has quit [Ping timeout: 246 seconds]
zpfvo has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
Chaser has quit [Ping timeout: 252 seconds]
sgw has joined #yocto
Chaser has joined #yocto
vladest has quit [Quit: vladest]
amitk_ has quit [Ping timeout: 240 seconds]
vladest has joined #yocto
speeder has quit [Ping timeout: 240 seconds]
Kubu_work has quit [Ping timeout: 246 seconds]
Vonter has quit [Ping timeout: 256 seconds]
Kubu_work has joined #yocto
Vonter has joined #yocto
joekale has joined #yocto
florian_kc has quit [Ping timeout: 252 seconds]
speeder has joined #yocto
speeder_ has joined #yocto
speeder has quit [Ping timeout: 252 seconds]
sgw has quit [Quit: Leaving.]
sgw has joined #yocto
davidinux has quit [Ping timeout: 255 seconds]
davidinux has joined #yocto
florian_kc has joined #yocto
goliath has quit [Quit: SIGSEGV]
xmn has joined #yocto
speeder__ has joined #yocto
speeder__ has quit [Remote host closed the connection]
Chaser has quit [Remote host closed the connection]
Chaser has joined #yocto
mvlad has quit [Remote host closed the connection]
joekale has quit [Quit: No Ping reply in 180 seconds.]
joekale has joined #yocto
leon-anavi has quit [Remote host closed the connection]
jmd has joined #yocto
neofutur_ has quit [Ping timeout: 260 seconds]
neofutur has joined #yocto
<khem>
RP: ok so I think the rcu stall is perhaps not connected, I increases the stall timeout from 21 to 60 and reran core-image-ptest-fast, I still had ssh timeouts but the stalls disappeared from qemu boot logs.
<khem>
RP: linux-yocto's default is 21s which is being hit regularly on my system
<zeddii>
I'm ok with changing the default, it can either be in a KERNEL_FEATURE that we only enable in the poky configs, or directly in all kernel's inheriting "standard".
asriel has quit [Quit: Don't drink the water. They put something in it to make you forget.]
Danct12 has joined #yocto
asriel has joined #yocto
<RP>
khem: I'm just wondering why as we really shouldn't hit that limit. Builds and tests in paralell and overloading the system?
prabhakarlad has quit [Quit: Client closed]
<khem>
perhaps yes, its running n number of ptests in parallel builds are all done
rfuentess has quit [Remote host closed the connection]
<khem>
zeddii: On Linus's tree I dont see CONFIG_RCU_CPU_STALL_TIMEOUT being set to 21 so is it our own config ?
<khem>
some arches e.g. mips/arm/s390/ppc explicitly set it to 60
<zeddii>
we don't have a setting for that in the kernel-cache, so it just takes defaults.
xmn has quit [Ping timeout: 256 seconds]
<khem>
ah default is 21 if not set nm
<khem>
yeah just checked kernel/rcu/Kconfig.debug
<khem>
I do see ubuntu and archlinux have overridden the defaults for all the supported arches to 60 so there must be conditions under heavy load
xmn has joined #yocto
florian_kc has joined #yocto
starblue has quit [Ping timeout: 264 seconds]
prabhakarlad has joined #yocto
nico39 has quit [Ping timeout: 250 seconds]
jmiehe has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
mvlad has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
mckoan is now known as mckoan|away
zpfvo has quit [Ping timeout: 246 seconds]
zpfvo has joined #yocto
jmiehe has quit [Quit: jmiehe]
jmiehe has joined #yocto
mbulut_ has quit [Ping timeout: 245 seconds]
florian_kc has quit [Ping timeout: 268 seconds]
prabhakarlad has quit [Quit: Client closed]
zpfvo has quit [Ping timeout: 256 seconds]
nerdboy has quit [Ping timeout: 255 seconds]
zpfvo has joined #yocto
neofutur has quit [Ping timeout: 256 seconds]
neofutur_ has joined #yocto
nerdboy has joined #yocto
nerdboy has joined #yocto
nerdboy has quit [Changing host]
jmiehe has quit [Quit: jmiehe]
jmiehe has joined #yocto
jmiehe has quit [Client Quit]
starblue has joined #yocto
pidge has quit [Remote host closed the connection]
prabhakar has quit [Ping timeout: 252 seconds]
<kanavin>
RP: I'm going to look into whether we can make selftest parallelize more efficiently. And look at at least the slowest tests in it and see if those can be sped up.
<kanavin>
there's just too much time spent doing tests sequentially towards the end, they should be given to other threads
<kanavin>
especially armhosts are a pain
<RP>
kanavin: I can give some tips?
<kanavin>
RP: maybe not yet, I'm trying to get the printdiff fixes into shape for sending for review
<kanavin>
I guess 'I'm going to' is a soft commitment, not a hard one :)
<RP>
kanavin: I suspect the biggest win would be looking at individual long running tests and optimising them. Parallelism works at the class level so any class of tests would run on the same "build" thread.
<kanavin>
RP: yes, but there's a particularly unfortunate allocation in there that runs for hours and hours long after all other threads have completed
<RP>
kanavin: FWIW I hate the way concurrenttest works behind the scenes and the way it shares out the tests is painful but I know why it works the way it does
<kanavin>
oescripts+sstatetests+wic one
<RP>
kanavin: the concurrency code barely works as it is :(
<RP>
kanavin: just sharing my experiences with this, I did what I could at the time
<RP>
kanavin: separating the long running unrelated tests into separate classes can help, as can tweaking the tests for performance
<kanavin>
RP: I also have to wonder, do we really have to run them 4 times across the spectrum of distros?
<RP>
kanavin: given the number of issues those show up, probably sadly
florian_kc has joined #yocto
florian__ has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
florian_kc has quit [Ping timeout: 260 seconds]
Kubu_work has joined #yocto
Saur_Home16 has joined #yocto
frieder has quit [Remote host closed the connection]
Saur_Home has quit [Ping timeout: 250 seconds]
Chaser has quit [Quit: Chaser]
Haxxa has quit [Quit: Haxxa flies away.]
Chaser has joined #yocto
Haxxa has joined #yocto
Chaser has quit [Ping timeout: 255 seconds]
pidge has joined #yocto
zpfvo has quit [Ping timeout: 256 seconds]
zpfvo has joined #yocto
zpfvo has quit [Ping timeout: 260 seconds]
zpfvo has joined #yocto
amitk has quit [Ping timeout: 256 seconds]
Saur_Home16 has quit [Quit: Client closed]
Saur_Home16 has joined #yocto
Saur_Home46 has joined #yocto
Saur_Home39 has joined #yocto
Saur_Home16 has quit [Ping timeout: 250 seconds]
Saur_Home46 has quit [Ping timeout: 250 seconds]
alperak has quit [Quit: Client closed]
alperak has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
florian__ has quit [Ping timeout: 252 seconds]
jmd has quit [Remote host closed the connection]
jmd has joined #yocto
jmd has quit [Remote host closed the connection]
jmd has joined #yocto
jmd has quit [Remote host closed the connection]
jmd has joined #yocto
jmd has quit [Remote host closed the connection]
jmd has joined #yocto
florian__ has joined #yocto
jmd has quit [Remote host closed the connection]
manuel1985 has quit [Quit: Leaving]
Saur_Home39 has quit [Quit: Client closed]
Saur_Home39 has joined #yocto
prabhakarlad has joined #yocto
olani has quit [Ping timeout: 255 seconds]
<alperak>
good night
alperak has quit [Quit: Client closed]
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
alessioigor has quit [Remote host closed the connection]