| Summary: | windows7tests slave: having trouble accessing build.eclipse.org | ||
|---|---|---|---|
| Product: | Community | Reporter: | Andrew Niefer <aniefer> |
| Component: | CI-Jenkins | Assignee: | Eclipse Webmaster <webmaster> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Andrew Niefer
You shouldn't need any proxy details for build. Certainly from the desktop I can reach build both via ping and firefox(which is configured to bypass proxies for eclipse.org). -M. Not sure what was wrong, the tests have started working again. This machine is having network problems again. When I change my hudson job to just do a ping, I get this: c:\hb\workspace\orion-jstest-windows>ping build.eclipse.org Pinging build.eclipse.org [172.25.25.57] with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 172.25.25.57: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), Also, from build.eclipse.org, I get this: e4Build@build:/shared/eclipse/e4/orion> ping windows7tests PING windows7tests.eclipse.org (172.30.206.143) 56(84) bytes of data. ^C --- windows7tests.eclipse.org ping statistics --- 10 packets transmitted, 0 received, 100% packet loss, time 9071ms Ok, I've forced builds IP in the hosts file. Should be ok now. -M. Closing. -M. |