Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
Seems lots of projects are having this issue. I have a new release of OpenPublish that won't build. Seems the build system is either majorly backed up or crashed.
http.lowSpeedLimit, http.lowSpeedTime: If the HTTP transfer speed is less than http.lowSpeedLimit for longer than http.lowSpeedTime seconds, the transfer is aborted. Can be overridden by the GIT_HTTP_LOW_SPEED_LIMIT and GIT_HTTP_LOW_SPEED_TIME environment variables.
We should set these in git config for bender on util. I'm not sure if environment variables would work or not since there are so many layers of subprocesses.
I'm seeing this trying to package a beta of BlogAPI_New: http://drupal.org/node/1872994 It has now been almost eight nine hours since I originally created the release node.
but it has not been effective. I think we should try setting http.lowSpeedLimit and http.lowSpeedTime in /etc/gitconfig on at least util and stagingwww, in puppet. The actual timeout should be long to allow slow servers to respond, but less than MySQL connection timeouts so that is not lost while waiting for Git.
re #30 - I think it packaged fine. Just takes a while. The release tag process now takes ~7 minutes and runs every 5 minutes so there's a max of 12 minutes from tagging to creation.
@greggles: It was over half an hour when I had last checked and it still hadn't been packaged/published. Maybe I was delirious and it actually wasn't that long. Either way, I gave up and went to bed rather than waiting for it. :)
Any chance this concerns also dev releases? The Title 7.x-1.x dev release is pointing to an outdated tarball. There have been a few commits since then.
Is there a problem with the packaging script today? I created a release last night and it does not seem to have fired yet. http://drupal.org/node/1971334
I may have done something wrong but thought I'd post here too.
Comments
Comment #1
kaushalkishorejaiswal commentedNo download links are available on this project page.....
Whats the problem?
Comment #2
kaushalkishorejaiswal commentedNo download links are available on this project page.....
Project Page URL : http://drupal.org/project/node_revision_delete
Whats the problem?
Comment #3
jec006 commentedSeems lots of projects are having this issue. I have a new release of OpenPublish that won't build. Seems the build system is either majorly backed up or crashed.
Edit: Link to my release that isn't built - http://drupal.org/node/1783650
Comment #4
arpieb commentedWebform Email Raw, 7.x-1.0-alpha2 has been hung since Sep 13 12:13a ET - no tarballs built, node unpublished:
https://drupal.org/node/1783150
Comment #5
gregglesThere was a 6.23 to 6.26 upgrade on d.o in the last ~36 hours that may have caused this. The security newsletters were broken for a bit yesterday until drumm found and fixed http://drupalcode.org/project/drupalorg.git/commit/90ecf3ceae3ff9b547e7d...
My guess is that something similar happened with packaging.
Comment #6
drummTaking this. I think there are two or more problems.
First, one of our packaging scripts, http://localhost:8080/job/package_release_nodes_tag/ hung for the last 13 hours. I kicked it and it is catching up. I expect it to complete in maybe 10 minutes.
Comment #7
drummThat build completed normally, release nodes should be packaged now.
The other issue I noticed is with recommended release calculation, which I'm testing on staging.
Comment #8
drummI believe this is all fixed up now.
Comment #9
kaushalkishorejaiswal commentedYes this has been fixed
Comment #10
killes@www.drop.org commentedSame happened again, today.
http://localhost:8080/job/package_release_nodes_tag/223427/console
Comment #11
bdragon commentedpackage_release_nodes_tag hung again today for 18 hours.
Comment #12
drummComment #13
drummThis started happening again about 20 hours ago. A remote git clone is hanging.
Comment #14
drummI filed #1854290: Add timeout to git operations to see about mitigating this in drush make.
Comment #15
drummFrom #1854290: Add timeout to git operations
git config has
http.lowSpeedLimit, http.lowSpeedTime: If the HTTP transfer speed is less than http.lowSpeedLimit for longer than http.lowSpeedTime seconds, the transfer is aborted. Can be overridden by the GIT_HTTP_LOW_SPEED_LIMIT and GIT_HTTP_LOW_SPEED_TIME environment variables.
We should set these in git config for bender on util. I'm not sure if environment variables would work or not since there are so many layers of subprocesses.
Comment #16
damienmckennaI'm seeing this trying to package a beta of BlogAPI_New: http://drupal.org/node/1872994 It has now been almost eight nine hours since I originally created the release node.
Comment #17
drummI reset this again. This also hung on
https://github.com/fgnass/spin.js.git. Packaging will take a few minutes to catch up.Comment #18
damienmckenna@drumm: Thanks!
Comment #19
gregglesI guess this was related to the github outages recently https://status.github.com/messages
Comment #20
drummHung on spin.js again:
Comment #21
drummhttp://localhost:8080/job/api.staging.devdrupal.org%20update%20src/ tries to work around this with
but it has not been effective. I think we should try setting
http.lowSpeedLimitandhttp.lowSpeedTimein/etc/gitconfigon at least util and stagingwww, in puppet. The actual timeout should be long to allow slow servers to respond, but less than MySQL connection timeouts so that is not lost while waiting for Git.Comment #22
drummStuck on spin.js again. #21 has not been implemented.
Comment #23
killes@www.drop.org commentedKilled another build process. This time it broke because this release https://drupal.org/node/1535950/release tried to download a file that doesn't exist.
Comment #24
drummHung on http://git.drupal.org/project/tmgmt.git this time.
Comment #25
drummHung on http://git.drupal.org/project/tmgmt.git again.
Comment #26
chx commentedShould we add a watchdog script?
Comment #27
drummWe haven't tried my idea in #21. I'm not sure where that configuration should live in Puppet.
Comment #28
_wdm_ commentedI have stuck project: http://drupal.org/project/composer_vendor
The 7.x-1.0 release has been created but the package stuff hasn't happend.
Comment #29
greggleskilles fixed this just now again.
Comment #30
dave reidhttp://drupal.org/node/1923158 (http://drupal.org/project/complete_profile) is stuck today. :/
Comment #31
gregglesre #30 - I think it packaged fine. Just takes a while. The release tag process now takes ~7 minutes and runs every 5 minutes so there's a max of 12 minutes from tagging to creation.
Comment #32
killes@www.drop.org commentedI actually had to stop a process. I've deleted the release that tried to package a non-existing release of something.
Comment #33
dave reid@greggles: It was over half an hour when I had last checked and it still hadn't been packaged/published. Maybe I was delirious and it actually wasn't that long. Either way, I gave up and went to bed rather than waiting for it. :)
Comment #34
jbloomfield commentedMy new alpha release of http://drupal.org/project/commerce_tnt is not packaging.
http://drupal.org/node/1924256 < this is the alpha release.
Any ideas. Thanks.
Comment #35
drummHung on http://git.drupal.org/project/tmgmt.git a couple times this weekend.
I added
to util's
/usr/local/etc/gitconfig, we'll see if it works.Comment #36
killes@www.drop.org commentedStill hanging on that project.
The issue that is reported in the jenkins output is about patching using
https://drupal.org/files/date_migrate_example_no_version_for_git_deploy-...
and others :(
Comment #37
twistor commentedhttp://drupal.org/project/cloudwords is stuck. It's been since last night.
http://drupal.org/node/1927686
Comment #38
drummStuck on http://git.drupal.org/project/entityreference.git this time. Killing that and it will catch up in the next few minutes.
Comment #39
drummStuck on
git-remote-http origin http://git.drupal.org/project/entityreference.gitagainComment #40
berdirSeems to hang again, created a -dev for http://drupal.org/project/past yesterday and it's not yet created: http://drupal.org/node/1932976
What's so special about tmgmt and entityreference? (I'm the maintainer of tmgmt, so if we're doing something wrong, I'd like to know :))
Comment #41
killes@www.drop.org commentedSadly it hung again.
I don't think there's anything special about tmgmt.
Comment #42
pwolanin commentedguess this is duplicate? http://drupal.org/node/1936938
Comment #43
plachAny chance this concerns also dev releases? The Title 7.x-1.x dev release is pointing to an outdated tarball. There have been a few commits since then.
Comment #44
haydeniv commentedIs there a problem with the packaging script today? I created a release last night and it does not seem to have fired yet. http://drupal.org/node/1971334
I may have done something wrong but thought I'd post here too.
Comment #45
drummIt got hung up on grammar parser this time.
Comment #46
sylus commentedIs this still a problem? My release has been hung up for past 24 hours @ http://drupal.org/node/1972380/release
Comment #47
perusio commentedThe same thing is happening to me. I even created a new tag to see if it changed anything.
https://drupal.org/node/1079612/release
No tarballs are created at all.
Comment #48
jbrown commentedReleases are not being published for http://drupal.org/project/persona
Comment #49
ti2m commentedSame for me here with a new dev release http://drupal.org/project/edge_suite
Comment #50
killes@www.drop.org commentedI've restarted the packaging jobs.
In the future, please create one ticket per module or release, this is too difficult to handle. Please always include a link to the release.
Comment #51
jbrown commentedSorry - I did create #1975850: Release node not being published, but I thought it would be better to have a single issue.
Comment #52
jbrown commentedThanks - my releases have appeared!
Comment #53
drupalninja99 commentedhttp://drupal.org/project/openchurch hasn't been working for at least a week now
Comment #54
gregglesre #53 - http://drupal.org/node/1524914 and http://drupal.org/node/1334928 point to drush errors that I think you can fix.
Comment #55
drupalninja99 commented@greggles I did fix those, it should have attempted to package again since then.
Comment #56
drupalninja99 commentedI think I fixed it. It was a core patch that no longer worked. I wish drush spit out more useful errors but I have this working now, thx!
Comment #57
Homotechsual commentedNVM - Just saw killes post.
Comment #58
killes@www.drop.org commentedthis is fixed. Please create new issues for any package not packaging.