Changes between Initial Version and Version 1 of Ticket #2357, comment 3
- Timestamp:
- 2015-01-09T02:23:30Z (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #2357, comment 3
initial v1 3 3 note: nondeterminism that results in obvious build failures is ok 4 4 different build targets can have different fingerprints 5 *what counts as a build target?5 what counts as a build target? 6 6 [NONDET: operating system versions, patches, variants, distribution if counted as the same target] 7 7 quickstart build flow: … … 19 19 [NONDET: which other Python packages installed on system and in virtualenv?] 20 20 [NONDET: PYTHONPATH] 21 * it has some set of URLs where it looks for package distributions ("dists") 21 22 it has some set of URLs where it looks for package distributions ("dists") 22 23 [NONDET: using the net at all is hopeless wrt determinism] 23 * which dists it chooses can influence further choices of dist for other dependencies 24 * try to build each dist 24 which dists it chooses can influence further choices of dist for other dependencies 25 try to build each dist 26 25 27 [NONDET: order of builds? not sure what algorithm is used] 26 *dists are either pure Python or have C/C++ code28 dists are either pure Python or have C/C++ code 27 29 [NONDET: buildchain for C/C++ code (includes many non-obvious dependencies)] 28 30 [NONDET: build process for C/C++ code] … … 32 34 [NONDET: do any dependencies rely on entropy sources (e.g. os.urandom)?] 33 35 [NONDET: can operations like running tests affect the built copy of Tahoe?] 34 *sources of nondeterminism from builds of dependencies36 sources of nondeterminism from builds of dependencies