From fc97f456dc2542b3d491bb3bcbd603becdc3e273 Mon Sep 17 00:00:00 2001 From: MilhouseVH Date: Sun, 7 Jul 2019 23:37:31 +0100 Subject: [PATCH] buildsystem: HACK: fix current status after initramfs initramfs is currently built from within linux:target which is a problem yet to be solved as it should be built as separately scheduled processes just like everything else. As we build initramfs from within linux:target, once initramfs is finished it emits an "UNLOCK" event which is the last event for the linux:target package until it too finishes, perhaps 5 or 10 minutes later. During this 5-10 minute period the dashboard gives the impression that initramfs is "stuck" in an UNLOCKed state when in fact processing continues within linux:target, which is now the "ACTIVE" package for the process slot. Until the initramfs scheduling problem is resolved, emit an extra "ACTIVE" event upon returning to linux:target correcting the dashboard (and also tools/mtstats.py elapsed time accumulation). --- packages/linux/package.mk | 1 + 1 file changed, 1 insertion(+) diff --git a/packages/linux/package.mk b/packages/linux/package.mk index 5cccf973df..e42a17e8f9 100644 --- a/packages/linux/package.mk +++ b/packages/linux/package.mk @@ -189,6 +189,7 @@ make_target() { rm -rf $BUILD/initramfs $SCRIPTS/install initramfs ) + pkg_lock_status "ACTIVE" "linux:target" "build" # arm64 target does not support creating uImage. # Build Image first, then wrap it using u-boot's mkimage.