| Summary: | test cvs repo for Eclipse platform CVS JUnit tests | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Community | Reporter: | Kim Moir <kim.moir> | ||||
| Component: | CI-Jenkins | Assignee: | Eclipse Webmaster <webmaster> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | ||||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Bug Depends on: | |||||||
| Bug Blocks: | 295393 | ||||||
| Attachments: |
|
||||||
|
Description
Kim Moir
Are there any issues with running this on the Hudson server itself? -M. no, I just need a repo to connect to :-) Ok I've created a CVS repo on hudson.eclipse.org, /cvs/org.eclipse.test. I'll send you the user and password separately. -M. I used your suggestion to store the credential information. Now I get this error message when running the cvs tests on the hudson slave. Error Message Could not connect to :pserver:hudsontest@hudson.eclipse.org:/cvs/org.eclipse.tests: I/O exception occurred: ProxyHTTP: java.io.IOException: proxy error: Forbidden Stacktrace org.eclipse.team.internal.ccvs.core.connection.CVSCommunicationException: Could not connect to :pserver:hudsontest@hudson.eclipse.org:/cvs/org.eclipse.tests: I/O exception occurred: ProxyHTTP: java.io.IOException: proxy error: Forbidden see https://hudson.eclipse.org/hudson/view/Eclipse%20and%20Equinox/job/eclipse-JUnit-Linux/121/testReport/org.eclipse.team.tests.ccvs.core/CVSTestSetup/unknown/ I'm unable to replicate this on the command line, or with my own test job. But based on the error it sure looks like the CVS connection is trying to use the proxy, which it shouldn't as the exception list should be *.eclipse.org. -M. If you look at the log here, I'm still seeing the problem. https://hudson.eclipse.org/hudson/view/Eclipse%20and%20Equinox/job/eclipse-JUnit-Linux/ws/ws/2010-11-19_14-53-14/eclipse-testing/linux.gtk-6.0_consolelog.txt You can try to run the https://hudson.eclipse.org/hudson/view/Eclipse%20and%20Equinox/job/eclipse-JUnit-Linux/ build and you'lll see the same issue again. I'm using hudson.eclipse.org as the hostname so I don't see why it would be using a proxy. I'm running the build but is there a way you can help me narrow the search to just a specific test we can run? -M. Sorry, I was testing stuff yesterday and was running all the tests. Let me change it again so it only runs the cvs tests. Okay I just ran it with only CVS tests. See https://hudson.eclipse.org/hudson/job/eclipse-JUnit-Linux/ You can run it again and it will only run that suite. Thanks. Well it sure looks like it's trying to connect via the proxy (from the logs): hudson-slave2 - - [26/Nov/2010:15:49:23 -0500] "CONNECT hudson.eclipse.org:2401 HTTP/1.0" 403 1041 "-" "-" hudson-slave2 - - [26/Nov/2010:15:49:23 -0500] "CONNECT hudson.eclipse.org:2401 HTTP/1.0" 403 1041 "-" "-" hudson-slave2 - - [26/Nov/2010:15:49:32 -0500] "CONNECT hudson.eclipse.org:2401 HTTP/1.0" 403 1041 "-" "-" hudson-slave2 - - [26/Nov/2010:15:49:33 -0500] "CONNECT hudson.eclipse.org:2401 HTTP/1.0" 403 1041 "-" "-" Is there a way I can run this test on the command line with some kind of debug flag so we can check what the environment looks like? -M. No debug mode per say. I just added -v for verbose to the ant call to run the script. You can also look at the log here.... https://hudson.eclipse.org/hudson/view/Eclipse%20and%20Equinox/job/eclipse-JUnit-Linux/ws/ws/2010-11-26_16-04-31/eclipse-testing/linux.gtk-6.0_consolelog.txt If you wanted to find out the value of some env variables you could add echo statements to the execute shell portion of the job. I created a simple ant task to try and replicate this, but it seems to work just fine. Here's the task: <?xml version="1.0"?> <project name="test-cvs" default="checkout" basedir="."> <property name="cvsroot" value=":pserver:hudsontest@hudson.eclipse.org:/cvs/org.eclipse.tests" /> <target name="checkout" <echo message="Checking out the required sources from CVS"/> <cvs cvsroot="${cvsroot}" command="login " /> <cvs cvsroot="${cvsroot}" command="co test " /> </target> </project> Using the -v flag with ant(1.7.1) shows me the environment seems to be set correctly. -M Did you run this on one of the slaves? If so, could you also write to the repo? I'm running it on slave2 as the hudson user (from the command line). I also tried it from the matt_test(https://hudson.eclipse.org/hudson/job/matt_test/23/console) job and it seemed happy. You'll need to give me some pointers on getting the job to commit something back to the repository(like how best to call mv or cp or vi ). It's possible my test is to 'simple' to accurately replicate what your build is doing. -M. Yes, I also wonder if there is an issue because there are a lot of files created on the filesystem at once with the cvs tests. Are there any firewall rules between the slaves that would cause connectionc to time out due to lots of traffic from a single ip? Can you give me admin rights on your job and I can modify it to run the entire test suite by just fetching a few zips and running a shell script? I've added you to the test job. I'm not aware of any firewall rules that 'discriminate' based on traffic levels. It's possible the servers service limit is being reached, but since your test is the only one I know of that uses this repository I'd be surprised if that was the problem. -M. You can run the matt-test build now and replicate the error. For instance https://hudson.eclipse.org/hudson/job/matt_test/54/testReport/junit/org.eclipse.team.tests.ccvs.core/CVSTestSetup/unknown/ Ok, so it looks like the job is detecting the 'no_proxy' environment variable, but using either eclipse.org or .eclipse.org don't seem to exclude hudson.eclipse.org services from being requested via the proxy. If I update runtests.sh to explicitly exclude hudson.eclipse.org it seems to be happy( https://hudson.eclipse.org/hudson/job/matt_test/60/console ) Can you try using the following set command(in either run tests or the hudson shell script) on your build to see if it resolve the issue? export no_proxy=localhost,dev.eclipse.org,hudson.eclipse.org If it works I can update the global settings to reflect this but I'll need to restart hudson and the slaves for it to take effect. -M. Created attachment 185095 [details]
patch
Thanks Matt, I'll run a test build for this once my existing Hudson test build has finished (testing some other bugs right now). Thanks this seems to have resolved the issue. |