Closed (fixed)
Project:
Drupal core
Version:
8.0.x-dev
Component:
base system
Priority:
Minor
Category:
Task
Assigned:
Issue tags:
Reporter:
Created:
16 Mar 2012 at 23:50 UTC
Updated:
29 Jul 2014 at 20:29 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
Crell commentedComment #4
Crell commentedComment #5
Crell commentedTrying again...
Comment #7
deviantintegral commentedPulling over the patch from https://drupal.org/node/1486960#comment-5772004
Comment #8
deviantintegral commentedComment #9
Crell commentedComment #11
Crell commentedComment #13
Crell commentedComment #15
Crell commentedComment #17
Crell commentedComment #19
Niklas Fiekas commentedTesting the over-all effects of the changes.
Comment #21
Crell commentedComment #22
Crell commentedComment #24
Crell commentedComment #25
Crell commentedMaybe it jammed? :-(
Comment #27
Crell commentedComment #29
Crell commentedComment #31
Crell commentedThat was totally wrong.
Comment #33
Crell commentedComment #35
Crell commentedTagging
Comment #36
cosmicdreams commentedComment #38
cosmicdreams commentedOK, I see what I'm doing wrong, I'm not diffing this code with Drupal 8 HEAD. This patch is my first attempt to do this kind of a patch.
Comment #40
cosmicdreams commentedThat's what I get for trying to use format-patch. Here's a regular git diff
Comment #42
cosmicdreams commentedThanks pifr for finding that. sorry I missed that. Hopefully this one passes.
Comment #44
cosmicdreams commentedthis one should be smaller and effect fewer files. It's curious to see $_GET['q'] be replaced by current_path() since current_path() returns $_GET['q']. Is this a mechanism to replace how the current path is retrieved in the future? should I spread the change of $_GET['q'] to current_path() to every part of drupal?
Comment #45
cosmicdreams commentedforgot patch
Comment #46
cosmicdreams commentedtesting a hypothesis, the only difference between this patch and 45 is that I've change 12 instances of $_GET['q'] in menu.inc and common.inc to current_path().
Comment #48
Crell commentedComment #51
Crell commentedComment #53
Niklas Fiekas commentedTesting how some changes perform.
Comment #55
Crell commentedStarting to get up there in size, but should be much better on the test front...
Comment #57
jthorson commentedOnce again, a testbot breaker ... or at least, a testbot plugger ...
Hopefully these can shed some light on things ... This is just a select excerpt; the first one is the most common by about 5 times.
Comment #58
sunAs long as testbots aren't shielded against this attack ;)
the best way to avoid taking them down is to run at least one of the failing test cases locally.
---
That said, since the PSR-0/classloader changes in D8, my local PHP 5.3.6 frequently manages to freeze and take down my local Apache server on fatal or more severe exceptions. Perhaps something similar is happening on testbots? At least I've the impression something odd is going on in our codebase.
Comment #59
Crell commentedThis is freshly merged from upstream to include the /index.php/ patch. Let's see what happens...
Comment #61
cosmicdreams commentedThis appears to be the showstopper:
Comment #62
Crell commentedComment #64
cosmicdreams commentedSearched through the code and found 5 or 6 instances where the frontpage settings were handled by variable_get, variable_set.
Fixed those and added some more debugging information. (which I will take out if this goes green)
Comment #65
cosmicdreams commentedwoops wrong issue, sorry
Comment #67
Crell commentedComment #69
cosmicdreams commented#67: 1463656-drupal-kernel.patch queued for re-testing.
Comment #71
neclimdulComment #72
aspilicious commentedComment #74
effulgentsia commentedThis is #71 plus language negotiation fixes. Depending on test results, I'll commit the interdiff to a suitable branch.
Comment #75
cosmicdreams commented#74: 1486960-kernel-testbot-74.patch queued for re-testing.
Comment #76
effulgentsia commented#74 changes some bootstrap logic that affects all non-index.php scripts, like the bot runner, which is why it ran 0 tests. This adds a temporary _drupal_bootstrap_legacy() function to work around that.
Comment #78
effulgentsia commentedSweet. That's a 90% failure reduction and 70% exception reduction. This should be the same from a test standpoint, but with a cleaner implementation.
Comment #80
cosmicdreams commentedtiny change, a typo may have made one of the tests to fail.
Comment #81
cosmicdreams commentedComment #83
Crell commentedComment #85
Niklas Fiekas commentedComment #86
Niklas Fiekas commentedUgg ... that should have beenWrong, too. Merge it and then diff next time...., not..-- poor testbot :/Comment #88
Niklas Fiekas commentedComment #90
Crell commentedComment #92
Crell commentedComment #93
aspilicious commentedYEAY!!! GREEN!!!
But I noticed something...
Tests are slowed down by 10! minutes with this patch.
Seriously? Why?
Comment #94
pounardCongrats!
Comment #95
cosmicdreams commentedOMG Green!
Reviewing...
Comment #96
andypostIs this a hack? Suppose better to add another array argument to url()
Comment #97
Crell commentedPlease don't post code reviews here. Let's keep those in the main thread. This issue is just for playing testbot pingpong. :-)
Comment #98
effulgentsia commentedThis is same as #1463656-118: Add a Drupal kernel; leverage HttpFoundation and HttpKernel but without the .htaccess change. I'm curious if that change is required for tests to pass.
Comment #99
Crell commentedeffulgentsia: Please remember to use the sandbox, since that's what we're merging from. Straight up patches are just duplicated work. :-(
Comment #100
Crell commentedComment #101
effulgentsia commentedSame patch as in #1463656-125: Add a Drupal kernel; leverage HttpFoundation and HttpKernel, minus xmlrpc.test changes. If this passes, I will open a separate core issue for that, and a wscci sandbox issue to remove it from the kernel work.
Comment #102
Niklas Fiekas commented@effulgentsia: Mhh ... looks like this has been solved (somehow) in the mean-time. Ensured it passes with clean URLs as well. I looked at the history and made sure it indeed failed at some point. Didn't bisect it, yet. But as long as it passes that's awesome. Do we even need a follow-up?
Comment #103
effulgentsia commentedYes. See #1593674: Remove unrelated change to xmlrpc.test for details.
Comment #104
effulgentsia commentedTiming testbot as part of #1578090: Benchmark/profile kernel. Will post analysis there.
Comment #105
Crell commentedComment #106
aspilicious commented#105: 1463656-drupal-kernel.patch queued for re-testing.
Comment #108
Crell commentedHopefully the last one...
Comment #109
cosmicdreams commentedAn attempt to reroll after all the PSR-0 tests were committed
Comment #110
aspilicious commentedYou're missing the node test stuff
Comment #112
Crell commentedHopefully for the last time...
Comment #113
aspilicious commentedA random doc review so I remember all these issues I found for followups.
I would group symfony stuff but thats just me
Do we need the first backslasg?
probabaly "@return string"
I still don't like this...
Has some undocumented functions, but is probably going to be rewritten...
This controller has a lot of functions with missing @return documentation.
Request should be removed
We should rewrite this in drupal api docs
Bigger than 80 chars?
26 days to next Drupal core point release.
Comment #114
pounardAgree.
Comment #115
Crell commentedThe kernel patch is now in(!), so we can close this issue, too.
aspilicious, can you open a new kernel-followup tagged issue with those tweaks?
GO TEAM!