| Summary: | Hardware/Software differences between epwin2 and epwin3 and effects on performance tests | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Oleg Besedin <ob1.eclipse> |
| Component: | Releng | Assignee: | Kim Moir <kim.moir> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | bokowski, daniel_megert, kim.moir, ob1.eclipse |
| Version: | 3.7 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
Oleg Besedin
(And, by the way, if two machines are identical why we are running tests on both?) Suggestions on actions: (a) Decommission epwin3 and forget about it (b) Run Windows benchmark software on both machines and compare results (c) Get a complete list of hardware pieces on both machines and see if there are differences (d) Run whatever tests are available for both machines to ascertain that epwin3 does not have a hardware problem Is the graphics card the same on both machines? As far as I know they are the same hardware. I'll ask Karl (our sysadmin) if the patch level is the same. They both run the tests on the same VMs. The reason that we have two machines is that Frederic wanted two as a sanity check. If one machine had strange results, you could look to the other machine. I agree that the test results are inconsistent and it wastes a time. As an aside, he rebooted both machines yesterday and applied patches so the machines should (in theory :-) be in a consistent state for today's build. Looking at the Java system properties there is a difference: on 'epwin2' the java.library.path has this additional entry: "C:\\buildtest\\jdk6_04\\bin" at the end. No idea whether this affects the result or not. What was the last time clean images had been installed on those machines? Is ti possible to re-image them in time for M7 milestone week? If not, RC1? We don't reimage the machines anymore. IT doesn't provide the facilities for us to reimage the machines anymore. Doesn't apply anymore. We are moving the build to eclipse.org hardware. |