Ticket #9070 (new defect)

Opened 6 years ago

Last modified 6 years ago

Remove Activity information from future build.log files

Reported by: mchua Owned by: mstone
Priority: normal Milestone: 9.1.0-cancelled
Component: distro Version: not specified
Keywords: cjbfor9.1.0 Cc: arjs, c_scott, mstone
Action Needed: never set Verified: no
Deployments affected: Blocked By:


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?

Change History

Changed 6 years ago by mchua

  • cc c_scott, mstone added
  • owner set to mstone
  • component changed from not assigned to distro

Changed 6 years ago by mchua

See http://blog.melchua.com/2008/12/04/what-versions-of-activities-are-shipped-with-g1g1/ for a description of the saga that inspired this ticket.

Changed 6 years ago by mstone-xmlrpc

  • keywords cjbfor9.1.0 added
  • milestone changed from 8.2.1 to 9.1.0

Pushing out to 9.1.0, per edmcnierney's request.

Note: See TracTickets for help on using tickets.