Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[cross-project-issues-dev] Would anyone be effected with Hudson slave named windows7tests being restricted for a few days?

A few days meaning specifically this Friday, 9/21 to Wednesday, 9/26.

We are doing some tests of tests in the Eclipse project (to see if our performance tests run on build.eclipse.org hardware). We've completed one on a "dedicated" linux slave with favorable conclusion, but would now like to do something similar for Windows.

This means the windows7tests Hudson slave would be reconfigured, and would have only one executor defined (only one job at a time would run).

Our performance tests would run for about 6 hours, then there would be a couple hours "break" where others could run, and then we'd hog the machine for another 6 hours (and so on, for this time period, assuming I can get it working at all ... which is just a statement about me, not Hudson or the performance tests :).

It looks like there are a few other jobs that use it at least occasionally:

IECrossfireServer-sign        
jetty-test-windows
orion-jstest-windows
tycho-its-win-nightly

I wanted to give this "warning" because I wanted to make sure we would not impact anyone's Kepler M2 deliverables, since I know that's just a few weeks away.

If you do have an issue, please comment in bug 374441
https://bugs.eclipse.org/bugs/show_bug.cgi?id=374441

If we don't hear anything in a day or two, we'll assume it will not impact anyone and proceed with that plan.
(Eventually, if you are wondering, there would be more "windows machines" configured so one could be "dedicated" to performance testing and others used for normal unit testing).

Thanks,

Back to the top