aboutsummaryrefslogtreecommitdiff
path: root/hurd/lookup-at.c
diff options
context:
space:
mode:
authorJoseph Myers <joseph@codesourcery.com>2016-11-26 00:10:24 +0000
committerJoseph Myers <joseph@codesourcery.com>2016-11-26 00:10:24 +0000
commitbf469f0ce98df9875daef625a85abd1160c44335 (patch)
tree62b684253b599e9d30900e4768b251db4719b6aa /hurd/lookup-at.c
parenta1c9859baf0b9a062bee6218e5e3402577b2c84e (diff)
downloadglibc-bf469f0ce98df9875daef625a85abd1160c44335.zip
glibc-bf469f0ce98df9875daef625a85abd1160c44335.tar.gz
glibc-bf469f0ce98df9875daef625a85abd1160c44335.tar.bz2
Make build-many-glibcs.py store more information about builds.
This patch makes build-many-glibcs.py store information about builds in JSON format. This is part of preparing it for use in a bot checking for regressions. The information stored is: time of last build (of host-libraries, compilers or glibcs); versions of components used in the last build (for compilers, host library versions are properly copied from those used for the previous host-libraries build, and for glibcs, component versions other than that of glibc are similarly copied from the last compilers build); PASS/FAIL/UNRESOLVED results of the individual build steps; a list of changed results; a list of tests (that are still run at all) that have ever been recorded to PASS. The first pieces of information are intended to be used by a bot to decide whether a rebuild is appropriate (based on some combination of elapsed time and changes to versions; a bot might want to rebuild glibcs if there had been any change but only rebuild compilers after enough time had elapsed, for example). All the information is intended to be used in generating mails with results information. This state is specifically for full builds (no individual configs for building compilers or glibcs specified). If individual configs are specified, build-time and build-versions information is cleared (since it will no longer accurately reflect the install directory contents), while the other information is left unchanged. This reflects the motivation of providing information for a bot checking for regressions; the contents of build-state.json in a tree used for manual builds that may be only for some configurations are not particularly important. * scripts/build-many-glibcs.py: Import datetime module. (Context.__init__): Load JSON build state. Initialize list of status logs. (Context.run_builds): Update saved build state. (Context.add_makefile_cmdlist): Update list of status logs. (Context.load_build_state_json): New function. (Context.store_build_state_json): Likewise. (Context.clear_last_build_state): Likewise. (Context.update_build_state): Likewise. (CommandList.status_logs): Likewise.
Diffstat (limited to 'hurd/lookup-at.c')
0 files changed, 0 insertions, 0 deletions