Re: unit tests - 1 fails locally, 38 fail on jenkins

From: Date: Sat, 07 Jan 2012 21:43:19 +0000
Subject: Re: unit tests - 1 fails locally, 38 fail on jenkins
References: 1  Groups: php.pear.qa php.pear.core 
Request: Send a blank email to [email protected] to get a copy of this message
On 7 Jan 2012, at 16:03, Daniel Convissor wrote:

> Hi Folks:
> 
> I've done some more work on the pear-core unit tests.
> 
> There is one test that fails when I run it locally:
> 	tests/PEAR_Command_Pickle/pickle/test.phpt
> 
> The difference is the following element is missing from the actual output:
> 	Tag the released code with "pear svntag package2.xml"
> 
> I'm guessing it may have to do with pear-core now being in git rather
> than svn.  
> 
> 
> Beyond that, there are 37 other unit tests that run fine via
> "phpunit -d error_reporting=22527 tests" on my local machine but are
> failing on the Jenkins server.  See the list at:
> http://test.pear.php.net:8080/job/PEAR/18/testReport/
> 
> Can someone with more knowledge of pear-core's workings please take a
> look at these 38 tests?

I can try to look at that soon but if someone gets there before me, that's fine! I'm
heading to the US next week so I'm not 100% sure of how much time I have in the next few days.

How do I run things on the Jenkins server? Could be hard to debug if I can't get them to fail
locally (seems you have that problem right now)
Is there a way for me to either go on the server to run the outputted ..php files by hand (and to
edit them) or can I fetch them somehow from the Jenkins interface?

Taking a quick peak at the results, the top 3 have an issue with the temp dir, and actually a few
others in between... maybe related to your recent commit of sys get temp dir?
I have not had time to review that patch fully but maybe dirname(__FILE__) or so was not only being
used for tmp directory purposes but also to link to package files and tgz - I am seeing a good few
tests failing due to invalid package files.

Temp problems:
http://test.pear.php.net:8080/job/PEAR/18/testReport/(root)/tests_/_var_lib_jenkins_workspace_PEAR_tests_PEAR_Command_Mirror_download_all_test_normal_channel_rest_phpt/
http://test.pear.php.net:8080/job/PEAR/18/testReport/(root)/tests_/_var_lib_jenkins_workspace_PEAR_tests_PEAR_PackageFile_Generator_v2_toTgz2_test_extsrc_phpt/

Example of invalid package where it shouldn't have been:
http://test.pear.php.net:8080/job/PEAR/18/testReport/(root)/tests_/_var_lib_jenkins_workspace_PEAR_tests_PEAR_PackageFile_Generator_v2_toTgz2_test_fail_phpt/
http://test.pear.php.net:8080/job/PEAR/18/testReport/(root)/tests_/_var_lib_jenkins_workspace_PEAR_tests_PEAR_Dependency2_test_checkPackageDependency_PEAR_url_phpt/

http://test.pear.php.net:8080/job/PEAR/18/testReport/(root)/tests_/_var_lib_jenkins_workspace_PEAR_tests_PEAR_Command_Package_package_test_bug11318_phpt/
This one is just odd... getNotes? Lacking a PEAR::isError somewhere in the test it self.

- Helgi


Thread (5 messages)

« previous php.pear.core (#9973) next »