Open solardiz opened 2 years ago
Can we try to load LKRG with log_level=3? From this log we can't tell at what stage of loading can be problematic
I'm a bit concerned that if we use non-default/debugging settings for LKRG in many of the CI runs, we might miss an issue that only affects real/default/non-debugging uses. Anyway, yes, I suppose we can update the CI setup to enable log_level=3
for
mkosi-boot (jammy)
. No idea if the problem will occur again, and if it will reoccur with this same distro vs. some other. I re-ran this failed job, and it succeeded. I think we'll soon need to setup some stress-testing using settings similar to what we use for CI, but on our/rented hardware, and thus running those jobs in tight loops as necessary to reproduce issues promptly.
I think that this issue is another case of https://github.com/lkrg-org/lkrg/issues/87 and that's why I think log_level=3
maybe can help gives us more information - it looks not related to LKRG itself.
https://github.com/lkrg-org/lkrg/runs/5029333618?check_suite_focus=true