Skip to content
Snippets Groups Projects
  1. Feb 27, 2025
  2. Dec 09, 2024
  3. Dec 12, 2024
    • Mike Hommey's avatar
      Bug 1935333 - Avoid trying to install dist toolchains when bootstrapping from... · 6707a5c1
      Mike Hommey authored
      Bug 1935333 - Avoid trying to install dist toolchains when bootstrapping from a spidermonkey standalone tree.  a=pascalc
      
      The auto-bootstrap code gracefully handles the lack of information as to
      what toolchains are available in spidermonkey standalone trees, but the
      fallback code path for when toolchains are not to be unpacked doesn't
      handle the situation.
      
      By making the toolchains themselves define whether they are to be
      unpacked, we can remove the fallback code path and use auto-bootstrap in
      all cases.
      
      This makes `mach artifact toolchain --from-build` stop requiring a
      manual `--no-unpack`, but `--from-task` still needs it because it
      can't infer that information, as it doesn't have the task graph.
      
      Original Revision: https://phabricator.services.mozilla.com/D231342
      
      Differential Revision: https://phabricator.services.mozilla.com/D231846
      6707a5c1
  4. Dec 06, 2024
  5. Oct 15, 2024
  6. Aug 27, 2024
  7. Aug 26, 2024
    • Mike Hommey's avatar
      Bug 1906191 - Change how ProcessHandler handles output_timeout.... · fff1f6e2
      Mike Hommey authored
      Bug 1906191 - Change how ProcessHandler handles output_timeout. r=releng-reviewers,gbrown a=test-only
      
      First and foremost, this undoes the patch for bug 1845125, which causes
      other problems (e.g. output being dropped past a certain point).
      
      The rest of the patch addresses bug 1845125 at the root: Ultimately, this
      is a similar problem to bug 1863675.
      
      wait is blocked on joining the stream reader thread, but the stream
      reader thread is blocked on readline because the process is finished but
      hasn't been waited on yet.
      
      So joining the stream reader thread after the process is known to have
      been finished is expected to work more reliably... except when a child
      has been spun up that keeps it alive. In this case, we just keep the
      reader thread working in the background, which is a similar strategy to
      what was done in bug 1863675.
      
      Differential Revision: https://phabricator.services.mozilla.com/D218389
      fff1f6e2
  8. Jul 19, 2024
  9. Jun 21, 2024
  10. Jun 17, 2024
  11. Jun 05, 2024
  12. Jun 04, 2024
  13. Jun 03, 2024
  14. May 31, 2024
  15. May 30, 2024
  16. May 29, 2024
  17. May 28, 2024
Loading