Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
The PIFT server needs to be installed on Drupal.org.
The PIFT server needs to be installed on Drupal.org.
Comments
Comment #1
Gerhard Killesreiter CreditAttribution: Gerhard Killesreiter commentedChad says it isn't ready yet.
Comment #2
hunmonk CreditAttribution: hunmonk commentedwaiting on http://drupal.org/node/198454
Comment #3
hunmonk CreditAttribution: hunmonk commentedphase one deployment is being handled at http://drupal.org/node/201769 -- we'll make this issue about turning on the returning of file test results to drupal.org, after we work out any remaining kinks in the testing platform.
Comment #4
hunmonk CreditAttribution: hunmonk commentednow that http://drupal.org/node/201769 has been completed, this is active again.
next step is to monitor the re-sending of test files. if that works, then we'll want to turn off re-sending for the rest of the test period so the testbed doesn't get overwhelmed.
after that, we just need to review test results to make sure the testbed is working ok, then we can finish up this task
Comment #5
catchHad a skype chat with Rok Zlender, hunmonk and pwolanin today about this - quick summary:
t.d.o reporting back fails to d.o was enabled at Drupalcon, but it was testing multiple patches on individual issues at the same time, resulting in duplicate posts marking to needs work, or marking needs work based on old patches when the latest one was OK. Rok switched it off again after a few people complained.
This was because using simpletest to post results back bypasses PIFT's own methods of tracking which patches have been tested already.
Due to the way t.d.o and d.o communicate about testing status of individual issues (patches are tracked more than issues themselves), it'll be relatively hard to fix this issue if we continue to bypass PIFT for posting back results on d.o.
To do it properly, #271216: abstract comment creation functionality needs to go in first, then it's trivial to implement on the PIFT side. Hunmonk said he'd be more available from the beginning of next week at the latest, so would make reviewing that patch his first priority - of course anyone else is welcome to review it before then too :)
Once that's done, it should be easy to re-enable this.
Until reporting back is running, there's not much point in worrying about actual test runs on t.d.o - just patches which fail to apply would be a big help, and the reporting of failed test runs would be via the same method anyway.
That's about it, marking postponed until http://drupal.org/node/271216 is fixed.
Comment #6
boombatower CreditAttribution: boombatower commentedBased on my recent work:
and talks with hunmonk in IRC we should be able to get t.d.o running tests on patch with actual SimpleTest suite running!
We will work on reporting back to d.o and exact patch testing criteria once this is up.
From my understanding hunmonk installed the abstract comment patch on d.o, he updated the PIFT code to 6.x and added a hook in integrate with my new 6.x code, and he will re-install t.d.o with these changes. I have implemented the hook in the latest PIFR code and left him a not with druplicon.
If anything is incorrect let me know. Otherwise that is the current state.
Comment #7
boombatower CreditAttribution: boombatower commentedCorrection, hunmonk will not install framework on t.d.o.
Talked with amazon and we are attempting to get me root access to setup the new testing framework.
Recently I have made a large number of upgrades to the framework which should make it even more robust and able to "self heal" when slave servers crash.
Comment #8
Amazon CreditAttribution: Amazon commentedBoombatower, confirmed you have the necessary perms.
Comment #9
dwwI'm all for this effort, this is going to take drupal development another big leap forward.
I'm just curious what site(s) boombatower now has root on and what exactly he's going to be installing/changing. I had long discussions with hunmonk and others about the architecture of this whole thing when it was first getting off the ground, and helped stamp out potential security problems before they ever got past the drawing board stage. It's also hard on *.d.o these days to keep track of who's responsible for what and who's changing what and why. It's already been problematic at times just coordinating project* related deployments/changes between killes, myself and hunmonk. The more clearly defined boombatower's role on the *.d.o infra will be, the better. That goes for all of us, of course, but as we're adding more cooks to the kitchen, let's try to keep things organized lest we all spoil the soup. ;)
Thanks!
-Derek
Comment #10
boombatower CreditAttribution: boombatower commentedTesting.drupal.org is running. We will see how well it works and possibly perform some stress tests.
My blog post about the recent progress and what is left can be found http://blog.boombatower.com/testing.drupal.org-is-running!.
Comment #11
Amazon CreditAttribution: Amazon commentedDerek, boombatower is working on the testing.drupal.org server only. That server is not managed by Drupal.org but is donated by IO1.biz. Chad is doing all the PIFT work on the d.o infrastructure.
Kieran
Comment #12
dwwyay all around. thanks, everyone.
Comment #13
boombatower CreditAttribution: boombatower commentedCurrently waiting on the three issues to be completed.
Then I need to upload the new code that I wrote to t.d.o and away she goes....
Comment #14
boombatower CreditAttribution: boombatower commentedIssues completed...both d.o and t.d.o have new code...and have sending queues reset.
Testing.
Comment #15
boombatower CreditAttribution: boombatower commentedThis is working...now once we confirm it is stable we will add CNW.
Comment #16
hunmonk CreditAttribution: hunmonk commentedwaiting on #326184: review test results for accuracy
Comment #17
boombatower CreditAttribution: boombatower commentedCNW: #325481: Mark issues as CNW when most recent patch has failed testing
Friday: http://drupal.org/node/329973