Skip to content
Started 7 mo 22 days ago
Took 2 hr 4 min on workermtahpc
Success

#2044 (Oct 29, 2023, 12:50:09 AM)

Build Artifacts
Changes
  1. prefer old-style import "=>"; (detail / hgweb)
  2. merged (detail / hgweb)
  3. redundant (see also 3069da1743bc); (detail / hgweb)
  4. removed obsolete table (see also 6acd1a2bd146); (detail / hgweb)
  5. more robust init_database();
    proper treatment of views, not tables (amending dd350a41594c); (detail / hgweb)
  6. proper private_data.transaction_lock;
    prefer execute_batch_statement; (detail / hgweb)
  7. clarified names; (detail / hgweb)
  8. proper support for SSH; (detail / hgweb)
  9. tuned signature; (detail / hgweb)
  10. tuned imports; (detail / hgweb)
  11. add module for faster scheduled builds; (detail / hgweb)
  12. always use host database and make protected; (detail / hgweb)
  13. read relative cpu from build log; (detail / hgweb)
  14. prefer extensible next_node_info in build process over process_options in build engine (which needs the final node info anyway); (detail / hgweb)
  15. added start date to build jobs, e.g., for build time estimation; (detail / hgweb)
  16. added initial version of benchmark module, e.g., to compare performance of different hosts;
    added benchmark operation to build cluster; (detail / hgweb)
  17. generalized node infos: allow addressing of numa node segments via relative cpus;
    add more node options and process policy options using taskset as alternative to NUMA for more fine-grained cpu controls (e.g., for cpus with heterogeneous cores in the same NUMA segment); (detail / hgweb)
  18. add information about static host resources such as available NUMA nodes, cpus, etc. (e.g., for offline build planning); (detail / hgweb)
  19. added Range object to Host, e.g. to parse/unparse NUMA node ranges; (detail / hgweb)
  20. defined statically known tables of Build_Log;
    read hostname from build logs, store in Session_Entry (e.g., to track hosts in distributed build); (detail / hgweb)

Started by an SCM change

This run spent:

  • 8.4 sec waiting;
  • 2 hr 4 min build duration;
  • 2 hr 4 min total from scheduled to completion.
Revision: 6fdcd6c8c97ae7ffff4f2342851069867c46eba7