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: Monday, May 21,
2012 8:26 AM
Subject: Re: [PHP-QA] Parallel run-tests
On 21/05/2012 06:45, Nuno Lopes wrote:
Hi Zoe,
Thanks
Message- From: zoe slattery Sent: Monday, May 21,
2012 8:26 AM
Subject: Re: [PHP-QA] Parallel run-tests
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
-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: Monday, May 21
in that case the parallel version will fail.
No, it doesn't. That was a stupid bug and I fixed it last night :-)
Zoe
Nuno
-Original Message- From: zoe slattery
Sent: Thursday, May 17, 2012 1:00 PM
To: internals@lists.php.net ; PHP QA
Subject: [PHP-QA] Parallel run-tests
Hi
Over
On 21/05/2012 08:59, Devis Lucato wrote:
Hi,
nice work, out of curiosity I tried on a VM with 24 virtual cores:
Sequential new phpruntests: 29.6 seconds
Parallel -z 4: 12.1 - 12.3 secs
Parallel -z 8: 10.6 - 10.9 secs
Parallel -z 16: 10.6 - 11.3 secs
Parallel -z 24: 10.9 - 11.7 secs
Cool -
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:
[...]
HI Felipe - a couple of updates.
1) Is your ~/dev/php5_4/sapi/cli/php built --with-zlib?
2) This test uses the php-cgi, are you setting it with an env
variable? Or relying on run-tests.php to find it (it should do that)
Even if it is missing zlib function that is causing the initial error,
Hi
A few people were able to use the new run-tests.php code to run tests in
parallel on different platforms. I've plotted the results here:
http://zoah.co.uk/update-parallel-run-tests-php.
Thanks very much for doing that, thanks also for the bugs you found in
doing so (blush) - I will fix.
Hi
Over the past couple of weeks I have updated the parallel run-tests
(fixed a couple of minor bugs in the PHP code and the build.xml), it's
now almost at the point where I could go ahead and implement the last
pieces. Here is a summary and a few questions:
1. In rebasing the code the the
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 executed
Hi Miah -
Any chance you could write up the steps you took to test this - or point
me in the right direction so I can try myself?
Re 8 way, is that 8 physical or 8 threads? If I can get the tests
running I can give you a data point for a 4 core/8 thread i7 under
linux.
that would be brilliant!
Hi
When we implemented these sections in the parallel version of
run-tests.php we seem to have decided to change the way that they work.
https://wiki.php.net/qa/runtests/decisions/notimplemented
I can't find any discussion of this either on internals or on QA.
In the current version of
not
forget my initial requirements, such as e.g. mysql and mysqli tests
cannot run at the same time).
Nuno
-Original Message- From: zoe slattery
Sent: Thursday, May 03, 2012 11:54 AM
Subject: [PHP-QA] running tests in parallel?
Hi
Some years ago (in 2009) Stefan Priebsch, myself and a GSOC
Hi
Some years ago (in 2009) Stefan Priebsch, myself and a GSOC student
worked on a version of run-tests.php which would run tests in parallel -
I wrote about it here:
http://zoomsplatter.blogspot.co.uk/2009/07/on-no-not-more-tests.html.
The code was complete apart from finding some way to
Derick Rethans wrote:
On Wed, 17 Oct 2007, jean jayet wrote:
i have the following naive question : how can get a reference of test
results
smth to be able to find :
such set of test case id MUST pass
such set test case id MUST fail
such set test case id skip if such extension missing
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 :)
Hi guys - There is an alternative patch if you have't already committed
this. The line:
if (preg_match(/^$wanted_re$/s, $output))
can just be changed to remove the s modifier, I was working on trying
to fix up the tests and make sure that they all work. The problematic
ones are the php_info
..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
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
Marcus Boerger wrote:
Hello Nuno,
Thursday, September 13, 2007, 9:20:51 PM, you wrote:
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.
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'm not having
Marcus Boerger wrote:
I meant %s = [^\n]+?
Ah - I should have guessed that. Yes, it solves the problem, but then
running make test gives an extra 7 failing tests - so I need to look at
why they are failing and work out how to fix them.
and continuing our private discussion earlier we
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 and they don't work
:-( ).
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's a
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--
precision = 14
--FILE--
?php
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--
precision = 14
small number - but how small?
Zoe Slattery
IBM
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
about the compiler or special tools.
Ideally, including the dependent elements too (SDK, .NET, etc).
Regards and thanks up front!
Richard.
On 15/06/07, Zoe Slattery [EMAIL PROTECTED] wrote:
Rob, Pierre, Stanislav - thank you!!!
I have PHP6 building with a free development environment
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
unicode(10) const in A
Zoe Slattery
IBM
--
PHP Internals - PHP
. 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
--
PHP Internals - PHP Runtime
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 Mailing List
To unsubscribe
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 List
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: http
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 the related
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
? 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 Development Mailing List
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. For that
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 looks at
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 modes
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 have two
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
--
PHP Internals - PHP Runtime
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
Hi all
We added a few tests for array, string and variable handling functions
at the weekend. As always - any feedback will be welcome.
One thing we had some difficulty with was keeping the test output small
enough to be easily read. We chose to divide up tests like this:
Hi Marcus
Thanks - that answers the question ...and test cases are on their way:-)
I have just committed 3 tests in the PHP 6 stream (strcasecmp, strcmp,
strlen) and would very much appreciate any feedback on them. We are
aiming for both line coverage and functional coverage, it would be good
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 a
Hi - I wonder if anyone could help me with a testing question?
We have written a few additional test cases for string functions which I
was about to check-in, then I noticed that the test cases pass OK if I
use the php.ini-dist file and fail if I don't specify an file (ie use
all default
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
49 matches
Mail list logo
