Many times, the original base kernel used (e.g. 2.6.11-
rc3-mm2) for patches has compile failures for defconfig
or allxxxconfig for many architectures. When a developer
submits his/her own patch to the base kernel and
requests tests, the resulting build output shows all
these failures. It's painful for the developer to track
down all the failures to see if his/her patch introduced
any new failure or whether they existed in the base.
PLM/STP would save a lot of developers a lot of time if
it showed whether the compile/cross-compile errors
were specifically introduced by the developer submitted
patches or whether they existed in the base kernel build
used as the starting point.