openembedded-core.git/meta/classes/rm_work.bbclass, branch morty

rm_work: Ensure we don't remove sigbasedata files

2016-11-16T10:34:34+00:00

We don't remove sigdata files, we also shouldn't remove sigbasedata files
as this hinders debugging.

(From OE-Core rev: 988349f90c8dc5498b1f08f71e99b13e928a0fd0)

Signed-off-by: Richard Purdie

rm_work: don't remove timestamps of image tasks

2016-08-23T16:44:17+00:00

Excluded removal of do_bootimg, do_bootdirectdisk and do_vmimg
timestamps to prevent unneeded rootfs rebuilds.

[YOCTO #10159]

Signed-off-by: Ed Bartosh 
Signed-off-by: Ross Burton

classes/rm_work: use the idle I/O scheduler class

2016-06-15T16:36:36+00:00

As rm_work is just cleanup it shouldn't starve more important tasks such as
do_compile of I/O, so use BB_TASK_IONICE_LEVEL to run the task in the idle
scheduler class.

Signed-off-by: Ross Burton

rm_work: exclude all kernel recipes

2016-06-06T14:44:04+00:00

* otherwise kernel is rebuilt every single time and often it fails when
  building external modules

[YOCTO #9352]

Signed-off-by: Martin Jansa 
Signed-off-by: Richard Purdie

classes: Fix do_rootfs references

2016-01-11T15:54:34+00:00

After the separation of do_rootfs, some rootfs references need changing
to image_complete.

Signed-off-by: Richard Purdie

rm_work.bbclass: Exclude do_rootfs stamp removal

2015-11-16T11:28:50+00:00

This prevents unneeded rootfs rebuilds if the metadata has not changed
while using rm_work.

Signed-off-by: Jate Sujjavanich 
Signed-off-by: Ross Burton

kernel/rm_work: Improve interaction

2015-05-15T11:05:52+00:00

The do_shared_workdir task does leave behind the necessary information in
shared-work after it completes. We don't make this a "full" sstate task
however since that means tarring up and copying what is usually a large
amount of data which would be better extracted straight from the original
SCM.

The issue with rm_work occurs since it removes the do_shared_workdir stamp
meaning subsequent builds will add it back if they need to touch any kernel
modules for example. This ends up triggering a near enough complete kernerl
rebuild since if configure reruns, populate_sysroot has to rerun.

This change promotes the task to have a "setscene" variant but it doesn't use
any of the sstate class lifting to generate the sstate file. The sstate function
will therefore never get called since the sstate object will never exist.

We can add the task to the list of tasks rm_work promotes to a setscene variant
and unwanted rebuilds of the kernel should be avoided.

Signed-off-by: Richard Purdie

rm_work: Fix RM_WORK_EXCLUDE for image/sdk recipes

2015-01-07T23:48:24+00:00

A previous change meant image/sdk recipes were removed unconditionally
by the class and did not respect RM_WORK_EXCLUDE. This fixes that
problem.

[YOCTO #7114]

Signed-off-by: Richard Purdie

rm_work: Speed up rootfs/populate_sdk removal

2014-10-24T20:59:42+00:00

Commands like bitbake X -c rootfs or bitbake X -c populate_sdk do not
trigger rm_work to clean up the directories afterwards since it
traditionally hooks onto do_build. This change means those two tasks now
clean up after themselves. We use the cleandirs function attribute to
handle this.

[YOCTO #6413]

Signed-off-by: Richard Purdie

rm_work.bbclass: ignore failure for removing pseudo folder

2013-05-24T13:14:30+00:00

When building over NFS2/3 server, removal of pseudo folders will fail in
some cases for there are files in it still used by pseudo daemon, thus
cause ".nfsXXXXX" files generated which can't be removed by clients. This
will lead rm_work task fo fail.

These failures could be safely ignored because ".nfsXXXXX" files would be
automatically cleared by NFS server when no clients keep opening them.

[YOCTO #4531]
[ CQID: WIND00412051 ]

Signed-off-by: Ming Liu 
Signed-off-by: Saul Wold