thing seems to be to map these to specific processors - that's
easy enough and requires no difficult code. There are more elegant
solutions of course.
Zoe
Hi Nuno
Hi,
Here you have a dump of a run of PHP_HEAD in the gcov machine (almost
13k tests) without valgrind:
htt
implemented, I have tested it using ext/pdo_mysql and
ext/pdo_sqlite.
I'm testing using about 8000 phpt tests and getting the same results
as run-tests. There is still work to do on performance but I think it
might at this stage be worth trying a bigger sample.
Zoe
Alright, thanks for the r
run-tests. There is still work to do on performance but I think it might
at this stage be worth trying a bigger sample.
Zoe
Alright, thanks for the reply!
I'll try to have a look at the code and give it a try next weekend.
Nuno
-Original Message----- From: zoe slattery Sent: Mond
pTestRun.php on line 107
PHP Notice: Undefined offset: 1 in
phpruntests/src/testrun/rtPhpTestRun.php on line 107
My bad. I started to implement REDIRECTTEST and checked in some initial
changes, I can see what I've done wrong and will fix later today.
Zoe
Devis
On 21/05/2012 06:45, Nuno Lopes wrote:
Hi Zoe,
Thanks for undertaking this project!
I just have a few concerns about this:
- The speedup seems a bit low to me. Maybe with a higher number of
extensions enabled it will improve?..
I don't think it will improve with a higher number of exten
s
is specific to the number of processes that are being run I'd need to
put some extra debug in I think.
Thanks, Zoe
Thanks, Zoe
Notice: Undefined offset: 0 in
/home/felipe/dev/phpruntests/src/testcase/rtTestDifference.php on line
91
Fatal error: Allowed memory size of 134217728 bytes ex
On 19/05/2012 22:33, Felipe Pena wrote:
Hi Zoe,
great work on this new run-tests! :D
I was testing it and noticed a problem when running using the following command:
$ ~/dev/php5_4/sapi/cli/php run-tests.php -z 8 -p
~/dev/php5_4/sapi/cli/php ~/dev/php5_4/
It shows the PHP messages
completing the implementation and fixing bugs has a higher priority for me.
Zoe
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
! I have a the steps written down in various
places - a bit scattered around :-/
I'll assemble a list of instructions and put it on the PHP wiki later
tonight, then I'll send out a link.
Thanks so much for the offer!
Zoe
--
PHP Internals - PHP Runtime Development Mailing List
To u
Olivier - brilliant thanks!
So, we have two points now: http://zoah.co.uk/update-parallel-run-tests-php
Anyone do an 8 way?
Zoe
5. Testing. I'm able to do basic testing on Mac OSX and Linux
Hi Zoe,
Here is a quick test on my 4-cores Linux server :
tested on PHP 5.3.9
412 tests exe
to pick up this aspect I'd be happy to get them started.
Zoe
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
sense to just have a single --GZIP_POST-- section. Maybe I'm missing
something?
Anyway - it affects two tests (afaict) and I was wondering if there
would be any objection to my making a small change to the way these two
sections are implemented in run-tests.php? And change the tests of
Hi
Thanks for the replies to this thread - I'll get on with it then :-)
Zoe
It's very important! Take a look at http://gcov.php.net
A single build takes almost 2 days with most extensions enabled plus
valgrind testing.
So, yes, parallel testing would be highly appreciated (
and
would be happy to do this, however, I've been fairly out of touch with
PHP since 2009, so before I get on and make this work:
(a) Would it still be helpful if the tests could be run faster?
(b) Has anyone come up with a better solution in the years since I
looked at this?
Thanks
.com/buildbot/docs/0.7.10/
I might be able to sit down and give this a go on the plane next week.
Zoe
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Hey Gwynne
Zoe, have a look at <http://news.php.net/php.doc.cvs/4180> :). I
don't have anything that can read that ODP file you linked (at least,
not in any useful sense), but the opcodes.html file is all there.
With any luck, someone else will come along and clean it up a b
object? Or better still would anyone be willing to integrate
them with the PHP docs?
Zoe
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
-- sections
aren't the aren't the only problems. I've found a few sections called
--SKIP--, which of course do nothing :-).
I started a requirements page for the new code, here
wiki.php.net/qa/runtests, but I think it's better to discuss on the list
before adding th
mentor means helping answer user groups questions about
test writing and reviewing and committing their tests.
Please would you add your name and other details to the table here
wiki.php.net/qa/testfest if you can help with this?
Thanks, Zoe
--
PHP Internals - PHP Runtime Development Mailing
Hi Zoe,
Is there documentation on this change?
Hi Greg - you mean the change I made to the phpinfo.phpt test? If so I
changed it because it was failing and should not have been. Or do you
mean changes to run-tests.php options?
I'm finding it a little bit
arbitrary that run-tests
ing behaviour
is completely different so many of the PHP tests failed. I believe that
PHP should behave in a platform independent way - that is what the fix
to #42868 achieves. It is also fair to say that any applications that
depend on the overflow behaviour in PHP 5.2 cannot be guaranteed to ru
Hi all
I apologise for spamming both lists with this and also having blogged
first, I intended then all to go at the same time :-). We (Lukas, Scott,
Pierre and others ) have been talking about this a little on IRC and I
updated the QA web pages a while ago. We thought it was time to be a bit
Hi Lukas, Johannes
Please could I ask for a PHP5.3 release manager's point of view on this?
I raised this ext/imap bug yesterday
http://bugs.php.net/bug.php?id=46902 after a discussion with Ilia
because I noticed that all of the function return values which result
from a failure of parameter
Hi
I have some PHP opcode documentation which might be useful, an html
version is linked here: http://www.zapt.info/opcodes.html.
The hard work (writing the samples) was all done by Mich and Toyo. All
I've done is written some PHP and used a slightly modified VLD to be
able to automatically
.
Is there a list of what needs to be written? I have some spare time and
could help, although I confess I'd prefer to write in PHP.
Zoe
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
the
Wiki...
Zoe
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
drown and discussion on [EMAIL PROTECTED]
I think fixing this is a one line change to
qaweb/buildtest-process.php, I'm happy to make that if there is
agreement. Please let me know if it isn't as simple as this.
Thanks,
Zoe
--
PHP Internals - PHP Runtime Development Maili
if
agreed. :)
Felipe - Great work!! I'll wait for the patch to go in and then re-run
the tests that I'm still trying to debug to see if they pass.
Zoe
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
isn't any further feedback by this time tomorrow I'll commit.
Thanks for your help,
Zoe
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
are writing the test to run it as
a PHP script and look at the output on the screen.
Zoe
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
t.php.
Feedback welcome!
Zoe Slattery
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Rob Nicholson wrote:
Hi Zoe,
I notice also that the testcase generator and the testcases we have
been committing differ slightly from the conventions listed at:
http://qa.php.net/write-test.php . This was based on feedback we
received so I think that http://qa.php.net/write-test.php should
to put it and in the
end said I'd put it in the top level and move or remove it if anyone
disagreed. I'll move it.
Thanks, Zoe
zoe kirjoitti:
Hi - for any of you that are writing PHPT tests for existing
extensions - I put a PHP script called generate_phpt.php into PHP 5.3
yeste
er. In the meantime:
php generate_phpt.php --help
tells you what it's supposed to do.
Zoe
PS - It doesn't work for PHP6 right now because the {{{proto line is
different.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
adding a
--SKIPIFF-- to the test case), sometimes it's because of an
implementation difference - we can't tell till we see the output from
the test.
As Derick says, they should all pass :-)
Zoe
regards,
Derick
--
PHP Internals - PHP Runtime Development Mailing List
To uns
line end.
Only 4 tests were actually intentionally using %s to match over line
endings. From what you say it sounds as though many more of the PECL
tests behave this way?
Zoe Slattery
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Stanislav Malyshev wrote:
So we have at least three different views on concept.
It seems that patch will be delayed again. :(
I think we better spend time on figuring out the concept and then do
the patch than first do the patch and then discover we don't know how
it was supposed to work :)
Zoe Slattery wrote:
It is a nice patch - but I'm seeing some errors that I don't
understand yet when I use it - like this:
Warning: preg_match(): Compilation failed: missing terminating ] for
character class at offset 5 in /home/zoe/BUILDS/php52/run-tests.php on
line 1609
I&#x
ugh to take care of it only at
line endings, and if so where are we doing that?
best regards
marcus
It is a nice patch - but I'm seeing some errors that I don't understand
yet when I use it - like this:
Warning: preg_match(): Compilation failed: missing terminating ] for
char
Hi again
On second thoughts - cancel my last two notes - yours is a better fix. :-)
Zoe
Johannes Schlüter wrote:
Hi Nuno,
On Thu, 2007-09-13 at 20:20 +0100, Nuno Lopes wrote:
now i get the issue. It grabbs more than one line! This means
run-tests.php has to be fixed. The whole thing
..PS - here is a slightly longer explanation of how I got to the idea
that to removing the "s" modifier would be a better fix.
I did a little more work to understand how the regex matching for %s was
working in run-tests.php.
In the current version %s maps to .+? This *should* match one or
problematic
ones are the php_info and php_credits which rely on the %s matching over
line endings.
Zoe
The main changes are:
'%s' => '[^\r\n]+'
'%a' => '.+'
This means that some tests have to be fixed, but the majority passes. Most
important i
a
For that reason I think it would be better to strip of the line ending prior
to do the matching.
Yes - I think so.
Zoe
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Marcus Boerger wrote:
Hello Zoe,
%s = [\n]+?
I'm not sure what this would match? I think we need something that matches any
character but doesn't run over a line end? If so it would be more like [.\\n]+?
- although this isn't right either (as in, I've tried both
Marcus Boerger wrote:
Hello Zoe,
now i get the issue. It grabbs more than one line! This means
run-tests.php has to be fixed. The whole thing is designed under
the assumption that %s catches no new lines and hence only one
line.
That would be the best answer but I think it
Pierre wrote:
On 8/23/07, Zoe Slattery <[EMAIL PROTECTED]> wrote:
Hi - I've writing a few tests for the math extension and have a question
about floating point precision.
Here's a small example:
--TEST--
Test return type and value for expected input sin()
--INI--
preci
Richard Lynch wrote:
On Thu, August 23, 2007 10:28 am, Zoe Slattery wrote:
Hi - I've writing a few tests for the math extension and have a
question
about floating point precision.
Here's a small example:
--TEST--
Test return type and value for expected input sin()
--INI--
prec
ht to test for an exact number in this way? I was slightly
suprised that I got the same number from Windows and Linux (maybe I
shouldn't be).
If not, I could write the test above to check that sin 360 is zero
plus/minus some small number - but how small?
Zoe Slattery
IBM
--
PHP Internal
Hi Richard - finally done this, see here:
http://www-03.ibm.com/developerworks/blogs/page/phpblog
Please comment on the blog if you have suggestions for improvement .
Thanks
Zoe
Richard Quadling wrote:
I would be REALLY grateful if you could do the whole process with no
assumed knowledge
ently. The tests
have worked ealier this week or last weekend. I'm sorry, but I have no
time to investigate further.
--Pierre
H Pierre - I've just checked out and can't reproduce on Linux (Ubuntu
6.10), so I guess it must be fixed? Or platform specific?
Zoe Slattery
IBM
--
PH
B extends A {
const myConst = "const in B";
public static function test() {
var_dump(parent::myDynConst);
}
}
B::test();
A::test();
?>
--EXPECT--
string(10) "const in A"
string(10) "const in A"
--UEXPECT--
unicode(10) "const in A"
u
tting here that I'm going to rip it all out and
do it again :-) I'll write up the steps and make them available
somewhere then I 'll probably need to recuperate by working exclusively
on Linux for an extended period.
Zoe Slattery
IBM
--
PHP Internals - PHP Runtime Development Ma
the compiler so I hoped
:-) that they'd work together. The Platform SDK is 2003 SP1
Zoe Slattery
IBM
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Hi
Has anyone built PHP6 using Visual C++ Express Edition V8? The symptoms
I get are pretty well described in http://bugs.php.net/bug.php?id=39130
and I'm just wondering if this was fixed for PHP5 and not PHP6?
Zoe Slattery
IBM UK
--
PHP Internals - PHP Runtime Development Mailing Li
Pierre wrote:
On 6/5/07, Zoe Slattery <[EMAIL PROTECTED]> wrote:
Hi all
Would it be possible to have a Bugzilla category for test case bugs?
The only alternative seems to be to raise a bug against the
implementation - which doesn't seem quite right.
Why not simply put them in
Hi all
Would it be possible to have a Bugzilla category for test case bugs?
The only alternative seems to be to raise a bug against the
implementation - which doesn't seem quite right.
Zoe Slattery
IBM
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit:
John Mertic wrote:
Below is a link to my take on the redesign:
http://files.edin.dk/php/installer/snaps-html/index.html
(Warning - none of the links on the page go to anywhere)
+1 - looks better and makes getting the latest snap easier
--
PHP Internals - PHP Runtime Development Mailing List
T
core functions? Some of it
does at the moment (strings, array) but it would be good to put all the
variable handling tests in ext/standard/tests/variable_handling for
example. It's another thing we could do as we go along...
Zoe Slattery
IBM UK
--
PHP Internals - PHP Runtime Develop
Derick Rethans wrote:
On Tue, 15 May 2007, Zoe Slattery wrote:
I have some updates that I'd like to make to
ext/tests/standard/array/range.phpt, the updates work fine with
unicode.semantics=off but not with unicode.semantics=on. The problem seems to
be that the warning Notices tha
look like intentional behaviour but I'm
guessing it might well be something that isn't implemented yet.
So, my question is - is it reasonable/helpful to add a test in CVS that
I know will fail if it's in an area that is currently under development?
Zoe Slattery
IBM UK
--
PH
Zoe Slattery wrote:
Antony Dovgal wrote:
On 05/15/2007 12:44 PM, Zoe Slattery wrote:
We're on it :-) Will probably have a few more questions on Unicode
testing later, noticed that you are putting UEXPECT section in
tests- but need to understand the implemenentation plan first...
We hav
Antony Dovgal wrote:
On 05/15/2007 12:44 PM, Zoe Slattery wrote:
We're on it :-) Will probably have a few more questions on Unicode
testing later, noticed that you are putting UEXPECT section in tests-
but need to understand the implemenentation plan first...
We have two operation mod
Antony Dovgal wrote:
On 05/15/2007 11:52 AM, SoftVirus wrote:
Hello Zoe, Marcus & Tony,
Files names having _(basic|variation|error|object).phpt looks much
better.
File names _[0-9]*.phpt does not give much detail about what are the
functions being testing by this testcase until one look
Marcus Boerger wrote:
Hi Marcus & Tony
Hello Zoe,
that's pretty fine. Instead of _[bveo][0-9]?.phpt you could do
_(basic|variation|error|object)[0-9]{3}.phpt. Which is a tad bit better.
However those are just filenames helping you to find the correct test
file while developing.
cause quite a lot of the differences between php5 and php6
seem to be in the exact form of the error message. Using this doesn't
completely solve the problem anyway - I think some of the "v" tests will
will end up being test_name_v1, test_name_v2 etc.
Thanks, Zoe
IBM UK
--
PHP Int
Hi Marcus
Marcus Boerger wrote:
Then I saw you changed a hell lot of expectations from "(-%d)" to "(%i)".
While this pretty much works it drops an important detail of the expectation.
The old version was aware of the sign of the result while the new one is not.
That means that now you might fix
get to understand general principles that apply to other languages.
Zoe
IBM
Ilia Alshanetsky wrote:
Ca we have a project designed to improve code coverage of PHP by
creating .phpt tests? I may not seem like a complex project, but in
terms of improving PHP as a language it would be
se, but have a slight preference
for (b) because it's a more satisfactory test of the implementation.
What's your view? Or anyone else's?
Marcus Boerger wrote:
Hello Zoe,
we decided to go the --INI-- route to test as many configurations as
possible. And only for specific tests
s". I also find it rather
too easy to get the wrong php.ini file accidentally :-( so specifying
one is easier, even if it only contains default values.
Zoe
IBM
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
I've been looking at the php tests and would like to be able to contribute more
tests for basic PHP functions to help increase the test coverage and prevent
regressions when code is changed. I don't know how granular the CVS access
controls are so am not sure what is possible. I've been working
70 matches
Mail list logo
