Chasing Symfony HEAD. :-) This is just a straight up update of the 6 components we have in core right now. In particular, there's 2 changes that make it important to do now:

1) Symfony recently moved all of their component unit tests into the components, to make it easier to spin off the components. (Fabien and Lukas has been discussing that at DrupalCon Denver.) So it now includes all of the unit tests for the components we're using. That's why the patch file is so huge.

2) It includes a couple of commits I've added to HttpFoundation/HttpKernel to help with the kernel patch. Specifically, it makes it possible (I believe) to bridge to our existing error handling system without rewriting the whole thing right now. For that reason I am marking this as major since it blocks the kernel.

There are no other changes outside of the vendor directory.

Let the Drupal commit message show that this corresponds to Symfony commit ID b0a6956bdc0e9ae39adf28b38037a9a905322916. (For later tracking purposes.)

Files: 
CommentFileSizeAuthor
#10 1542710-without-traits-and-services1-1-test.patch1.05 MBBTMash
PASSED: [[SimpleTest]]: [MySQL] 35,414 pass(es).
[ View ]
#6 1542710.patch1.05 MBBTMash
FAILED: [[SimpleTest]]: [MySQL] Invalid PHP syntax in core/vendor/Symfony/Component/ClassLoader/Tests/Fixtures/php5.4/traits.php.
[ View ]
symfony-update.patch1.05 MBCrell
FAILED: [[SimpleTest]]: [MySQL] Unable to apply patch symfony-update_2.patch. Unable to apply patch. See the log in the details link for more information.
[ View ]

Comments

Status:Active» Needs review

Status:Needs review» Needs work

The last submitted patch, symfony-update.patch, failed testing.

Yeeeeeeeeeah....

Oh for the love of... can we just switch to Composer already? Really? This issue is a complete waste of time we shouldn't be wasting.

Sounds like a problem of patch... composition. *glasses* YEEEEEEEAHHHH

Status:Needs work» Needs review
StatusFileSize
new1.05 MB
FAILED: [[SimpleTest]]: [MySQL] Invalid PHP syntax in core/vendor/Symfony/Component/ClassLoader/Tests/Fixtures/php5.4/traits.php.
[ View ]

Ok, this is a reroll - hopefully, this patch works (I did a checkout on commit b0a6956bdc0e9ae39adf28b38037a9a905322916 from symfony on github and did a staged binary diff since that seemed to be what was causing part of the issue).

Status:Needs review» Needs work

The last submitted patch, 1542710.patch, failed testing.

Hmm, I delved a bit into what errors woudl pop up and there are 2:

PHP Parse error:  parse error in ./ClassLoader/Tests/Fixtures/php5.4/traits.php on line 3
Errors parsing ./ClassLoader/Tests/Fixtures/php5.4/traits.php
PHP Fatal error:  Cannot declare class Container because the name is already in use in ./DependencyInjection/Tests/Fixtures/php/services1-1.php on line 20
Errors parsing ./DependencyInjection/Tests/Fixtures/php/services1-1.php

The first is based on there being a php 5.4 test in there on traits. If we're on 5.3, that is going to fail (makes sense).

The second one is because the file declares the Container class even though Container is declared before it (use Symfony\Component\DependencyInjection\Container; on line 4 of the file)

It took me a while to try and install php5.4 but after installing it, the testbot would likely still run into the DependencyInjection test as I ran into it:

PHP Fatal error:  Cannot declare class Container because the name is already in use in ./DependencyInjection/Tests/Fixtures/php/services1-1.php on line 20
Errors parsing ./DependencyInjection/Tests/Fixtures/php/services1-1.php

So, we have one error that we need to try and figure a way around (ignore paths containing php5.4? @sun mentioned that this sounds like a core php bug?) but the DependencyInjection error stems from Symfony since you cannot redeclare classes. From what I can see, the test class is autogenerated by the PhpDumper class.

Status:Needs work» Needs review
StatusFileSize
new1.05 MB
PASSED: [[SimpleTest]]: [MySQL] 35,414 pass(es).
[ View ]

Here is a version of the patch that does not contain the 2 error-producing test files in question.

Status:Needs review» Reviewed & tested by the community

Let's get this in and unblock the kernel.

Status:Reviewed & tested by the community» Fixed

Committed to 8.x. Thanks!

Status:Fixed» Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

Issue summary:View changes

Fix typo.