#9070 NORM Not Tri: Remove Activity information from future build.log files
Zarro Boogs per Child
bugtracker at laptop.org
Thu Dec 4 17:20:26 EST 2008
#9070: Remove Activity information from future build.log files
--------------------------+-------------------------------------------------
Reporter: mchua | Owner:
Type: defect | Status: new
Priority: normal | Milestone: Not Triaged
Component: not assigned | Version: not specified
Keywords: | Next_action: never set
Verified: 0 | Deployment_affected:
Blockedby: | Blocking:
--------------------------+-------------------------------------------------
Builds and Activities are separate. Having Activity information in
build.log files seems to contradict this, and could lead to confusion for
those unfamiliar with our system.
For instance, Arjun was trying to find out what version of Measure shipped
with G1G1 machines, and came across
http://download.laptop.org/xo-1/os/official/767/jffs2/build.log, which
contains text like this:
{{{
16:25:30 URL:http://mock.laptop.org/repos/local.8.2/XOS/Measure-17.xo
[110428] -> "Measure-17.xo" [1]
}}}
One might reasonably assume that Measure v17 is included with build 767
(and subsequently begin to worry that an incompatible/out-of-date version
of one's Activity has shipped to thousands of donors worldwide, which
actually happened).
This is not the case. No version of Measure, or any other Activity, is
included with build 767; the G1G1 image is a superset of build 767 that
includes both that and Measure v20. The Activity-related text in build.log
files is potentially misleading, and there isn't any reason why it should
still be around, as far as I can tell; can we change our build scripts so
that build.log files don't contain Activity-related information for
subsequent builds?
--
Ticket URL: <http://dev.laptop.org/ticket/9070>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system
More information about the Bugs
mailing list