[MacPorts] #49759: git checkout should produce some output
#49759: git checkout should produce some output --------------------------+-------------------------------- Reporter: ryandesign@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.3.4 Keywords: | Port: --------------------------+-------------------------------- [https://build.macports.org/builders/buildports-snowleopard- x86_64/builds/38635 This buildbot build] was interrupted after the third of seven ports, because there was no output for 20 minutes. A git clone command was running at the time, but had not yet completed. Run locally on a fast network, that git clone completes in 2.5 minutes and the clone occupies 372MB. Run on the buildbot builder, the same command has only downloaded 211MB by the 20 minute mark. For whatever reason there is a slow network connection between our builder and this git server, at least right now. The git clone commands are being run by MacPorts base with the -q flag to suppress all output. Can we change this so that some output is produced while cloning, so that the buildbot knows the build is not stuck? I agree the buildbot should abort builds that don't produce output for a time, but they shouldn't interrupt file transfers which are just progressing slowly, and this shouldn't cause subsequent ports in the portlist not to be tried. -- Ticket URL: <https://trac.macports.org/ticket/49759> MacPorts <https://www.macports.org/> Ports system for OS X
#49759: git checkout should produce some output ---------------------------+-------------------------------- Reporter: ryandesign@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.3.4 Resolution: | Keywords: Port: | ---------------------------+-------------------------------- Comment (by ryandesign@…): I've repeated the build and it finished fetching in about 18 minutes this time, so the build is running. I'd like a more permanent fix though that doesn't rely on network conditions or whatever's behind the slowdown. -- Ticket URL: <https://trac.macports.org/ticket/49759#comment:1> MacPorts <https://www.macports.org/> Ports system for OS X
#49759: git checkout should produce some output ---------------------------+-------------------------------- Reporter: ryandesign@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.3.4 Resolution: | Keywords: Port: | ---------------------------+-------------------------------- Comment (by ryandesign@…): bzr fetches should also produce output to prevent slow fetches from causing a timeout; see #49812. -- Ticket URL: <https://trac.macports.org/ticket/49759#comment:3> MacPorts <https://www.macports.org/> Ports system for the Mac operating system
#49759: git checkout should produce some output ---------------------------+-------------------------------- Reporter: ryandesign@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.3.4 Resolution: | Keywords: Port: | ---------------------------+-------------------------------- Changes (by larryv@…): * cc: larryv@… (added) Comment: I am not sure whether just omitting `-q` would suffice. If not, we could also use `--progress`. Excerpting from the Git 2.10.1 `git-clone` man page: {{{ --quiet, -q Operate quietly. Progress is not reported to the standard error stream. --verbose, -v Run verbosely. Does not affect the reporting of progress status to the standard error stream. --progress Progress status is reported on the standard error stream by default when it is attached to a terminal, unless -q is specified. This flag forces progress status even if the standard error stream is not directed to a terminal. }}} -- Ticket URL: <https://trac.macports.org/ticket/49759#comment:4> MacPorts <https://www.macports.org/> Ports system for the Mac operating system
participants (1)
-
MacPorts