Re: 64-bit SGI account offer

On November 1, 2002 10:51 am, Sebastian Nohn wrote: > > -----Original Message----- > > From: Ilia A. [mailto:ilia@prohost.org] > > Sent: Friday, November 01, 2002 4:26 PM > > To: Sebastian Nohn; PHP Quality Assurance Team Mailing List > > Subject: Re: [PHP-QA] 64-bit SGI account offer > > > > > Disagree. It's just a verification. You can also more easy see when > > > something broke on a certain machine with a certain configuration. This > > > evening im going to take a look at the make-tests.php > > > > Well, there are only 3 possible test result states, FAILED,PASS > > or SKIP. If > > the test did not succeed we know it passed or was skipped for whatever > > reason. For the purposes of debugging I believe that data is for the most > > part meaning less. > > I would rather suggest to leave the "skip"-thing. > > Why? > > The answer is easy: > > With my way, we would KNOW that PHP runs on for example Tru64 with Oracle > 8.1.7 but not on Linux with 8.1.9. With your way we only would know that it > does'nt work on Linux 8.1.9. If a test did not fail, we know it worked or was skipped. Considering our current test suit comprises of some 362 tests and growing sending huge amounts of information, which for the most part is useless would be counter productive. Considering that many people do dev testing on their home computers, with non-broadband connections, sending 100k+ data chunks would be simply too slow. If we must, I'd rather send skipped test since in 90% of the cases they would comprise the majority of the tests. Ilia P.S. We currently have some 30-40 tests mysql/pgsql that are always skipped, simply because those tests require an un-restricted, passwordless connection to the database server. This is not the case on 99.99% of the systems, perhaps we should reconsider the usefulness of those tests?