I tagged and created a release for spark 8.x-1.0 alpha3 last night, at http://drupal.org/node/1827460
The package is failing with the following:
Packaging error messages
ERROR: /usr/bin/php /var/www/drupal.org/tools/drush5/drush.php --no-cache --include=/var/www/drupal.org/tools/drupalorg_drush make --drupal-org=core --drupal-org-build-root=/var/tmp/tag.27613/spark --drupal-org-log-errors-to-file --drupal-org-log-package-metadata=metadata-core.json /var/tmp/tag.27613/spark/spark/drupal-org-core.make spark-8.x-1.0-alpha3 failed with status 1
ERROR: Build for spark-8.x-1.0-alpha3 failed.
I can't confirm these fails locally using the --drupal-org argument.
I asked about this in #drupal-infrastructure today, and dww thought it was maybe because we don't have an up-to-date version of Drush? #1301978: Upgrade Drush to v5 on all servers Though I'm not sure, cos unless the command output there is lying, it seems to be running drush5 (not sure exactly which 5 version though, to be able to test... apparently elsewhere on d.o we're running 7.x-4.5, though).
dww also suggested it might have something to do with applying patches, but we've been applying patches in Spark since the beginning, and never had a problem with it until now. But for reference, here are our make files:
http://drupalcode.org/project/spark.git/blob_plain/refs/tags/8.x-1.0-alp...
http://drupalcode.org/project/spark.git/blob_plain/refs/tags/8.x-1.0-alp...
I don't see anything terribly different in there from alpha2, which packaged just fine:
http://drupalcode.org/project/spark.git/blob_plain/refs/tags/8.x-1.0-alp...
http://drupalcode.org/project/spark.git/blob_plain/refs/tags/8.x-1.0-alp...
The only other thing that I saw in the issue queue that looked a little similar was #1793426: 0 sites reported usage for a distribution packaged on Drupal.org, but that seems to be specific to a checksum error, which we're not getting here.
Any help on this would be appreciated, as it's currently blocking people from testing D8 functionality we're trying to get into Drupal core by feature freeze. :(
Comments
Comment #1
webchickOh, and as a basic troubleshooting measure (since at #1472052: Packaging issue for distribution while using dev releases it mentioned this might be intermittent), I did try deleting/re-creating the release, but no cigar.
I also find it a bit strange, that the output of the errors over in that issue contained more stuff after "failed with status 1" but this one does not. Hm.
Anyway, I am stuck. :(
Comment #2
gregglesAt least on util the file /var/www/drupal.org/tools/drush5/drush.php exists and is a Drush 5.4 installation which seems pretty recent.
Did you try building this locally using a similar command?
Comment #3
gregglesAhem...
So, maybe see if your version is different than the 5.4 and try again. Otherwise I don't have other ideas :/
Comment #4
webchickOk, thanks! Drush 5.4 helps narrow it down.
So I did
git checkout 7.x-5.4
from my ~/drush directory, which normally points at the master branch.Then I did:
Ah-ha! Well that'll do it.
Had that shown up in the output instead of a cryptic "status 1" I'm sure I could've worked that out myself. Moving to the Project queue.
Comment #5
webchickIncidentally, I believe the reason this failed is because that patch was done as git format-patch rather than a traditional git diff. Fortunately, looks like later versions of Drush don't have this problem. But let me know if that's another packaging system/infrastructure bug/feature request I should file.
Comment #6
jessebeach CreditAttribution: jessebeach commentedI think the problem is
git am
and binary data. The patch that failed had a deleted PNG file in it. The file was included in the patch as encoded, changing the file format from UTF-8 to binary.git am
failed to apply the patch with the deleted PNG. The problem doesn't exist withgit apply
. I rerolled the patch without the deleted file and posted that to #1137920: Fix toolbar on small screen sizes and redesign toolbar for desktop.Are we using
git am
to apply patches with the build system? I don't think that's possible because any patch created withgit diff
would fail with the message Patch format detection failed. This message occurs when the patch is created withgit diff
instead ofgit format-patch
and applied withgit am
.If we're using
git apply
to apply patches, then I'm not sure why it failed. It works fine for me on the original patch that failedWhereas
git am
fails like the build process did:We might just need to go in and delete that PNG file by hand instead of by patch.
Comment #7
jessebeach CreditAttribution: jessebeach commentedHere's the bit with the messed up data:
Comment #8
dwwIs this issue about debugging the specific packaging problem with spark, or is it about the thing in the title about the cryptic error messages?
If it's about the specific problem, I believe it's a bug in drush make that's been fixed and just needs to be deployed, in which case this should be in the infra queue and perhaps just marked duplicate with #1738358: Upgrade drush used for distro packaging to 5.7+ to avoid bugs in drush make.
If it's about the general problem of the sucky error propagation between drush make and end users, it can stay here in the Project queue, but then let's not get lost in the weeds about the specific problems with the patch that's failing to apply. ;)
Sorry for the troubles. Sadly, d.o distro packaging isn't as high a priority for me right now as the D7 port of d.o...
Comment #9
jessebeach CreditAttribution: jessebeach commented@dww, I assume this is a general issue with patches that include deleted binary files. I'm trying to understand why it failed. If the make system is using
git apply
, then the patch with the deleted PNG should not have failed. But it did fail to build. I assume we're not usinggit am
because any patch created withgit diff
would fail to apply. So, I'm just confused and trying to put as much data around the issue as possible.Comment #10
dwwCool, thanks. If you suspect this is a bug in how drush make applies patches, you'll have much better luck with an issue in the drush issue queue. Sounds like this is probably a different bug from #1528422: Patches no longer apply because of info file re-writing (which is linked from #1738358: Upgrade drush used for distro packaging to 5.7+ to avoid bugs in drush make) so maybe we should just move this issue there for now to get the drush maintainers eye's on this. I honestly don't have the bandwidth to follow drush development closely, so I have no idea what it's currently doing to apply patches.
There's probably still value in a project.module bug report about improving error propagation, but since this issue is already full of useful info about this specific packaging problem, maybe we should just start a new clean issue about the error propagation and leave this one for figuring out why drush make can't apply this patch. ;)
Cheers,
-Derek
Comment #11
jessebeach CreditAttribution: jessebeach commentedCool, I'm fine with moving the conversation over to #1738358 as a first step in attempting to resolve the build failures. I've made a note there and linked back to this issue.
#1738358-6: Upgrade drush used for distro packaging to 5.7+ to avoid bugs in drush make
I'm totally agnostic about tracking the error propagation in this issue or a new one. I'd probably just use this one since it's here already.
Comment #12
dwwspark 8.x-1.0-alpha4 is built now that #1738358: Upgrade drush used for distro packaging to 5.7+ to avoid bugs in drush make is done.
Do we still care about trying to do a better job propagating errors here?
Thanks,
-Derek
Comment #13
webchickI would say yes, because then people can solve their own problems without pinging busy d.o D7 sprinters. :D
Comment #14
dwwOkay, sure. Technically, all the distro packaging code is a d.o-specific plugin from drupalorg_project. Moving to a more appropriate queue.
I doubt anything's going to happen here until after the D7 launch of d.o, but we'll see what happens.
Cheers,
-Derek
Comment #15
drummSeems like this hasn't been a problem lately. If it is still an issue, #1854444: Upgrade drush used for distro packaging with drush make has a good chance of improving it.