Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 454576 - perftests needs "Locks and Latchs" and other upgrades
Summary: perftests needs "Locks and Latchs" and other upgrades
Status: RESOLVED FIXED
Alias: None
Product: Community
Classification: Eclipse Foundation
Component: CI-Jenkins (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: David Williams CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-12-09 09:26 EST by David Williams CLA
Modified: 2014-12-09 21:52 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Williams CLA 2014-12-09 09:26:30 EST
To (other) Hudson admins, I'm pretty sure I can make all these changes myself, but ... if something goes wrong, may need your help! 

See bug 454530 for why the "perftests" machine needs "locks" (in short, we have "tiny jobs" that get stuck in the queue behind really long jobs ... locks will allow 2 executors so the "tiny jobs" (100ms) can run, while at same time allow only one "performance test job" at a time. 

I think we need this change "right now" before M4 finishes. The remaining ones should wait until later in the week, after our M4 tests are finished. 

= = = = =

I'm going to try the "automatic" upgrade of several plugins that show up on the "update" page. 


= = = = = 

After that change, I'd like to "move up" to the latest Hudson available, again, through "automatic upgrade". This may lead to upgrade of other plugins. 

The primary motivation of upgrading is what I think is a bug ... some properties set via cascading jobs do not "stick" ... if still occurs in latest Hudson, I'll open a bug on Hudson.
Comment 1 David Williams CLA 2014-12-09 09:50:21 EST
Unfortunately increasing executors is "immediate". 
But for "locks" I have to restart the server. 

Blow by blow: 

I canceled the "peformance tests" (that ended up running for a small time "at the same time) but naturally let the "quick jobs" all run. I do need to wait for the "back end" part of the quick jobs to finish, which is where the data is retrieved by a job on 'build.eclipse.org'. 

Then I will define the locks, tweak configuration, and restart the two jobs I canceled: 

I20141208-0800
4.5.0
64b32dc2f62b15d5353bc08ec6985bccf84c5455
otherPerformance

I20141208-2000
4.5.0
2ea3d8b168d30d17911c388ba4c8ff2d85c975d5
selectPerformance
Comment 2 David Williams CLA 2014-12-09 11:13:22 EST
So far, so good. 

The only complication was there seemed to be no direct way for me to "restart" the server. But, I put it in "going to shutdown" state. And then "work around" the restart problem, by "updating" the out of date plugins, at the end of which I am prompted to "restart server". 

There must be an easier way ... or, a plugin to install :)
Comment 3 David Williams CLA 2014-12-09 21:52:12 EST
I'm going to count this as fixed, since I had to update the plugins, just to trick it into re-starting. 

I'll open new one when I want to upgrade or install new plugins.