Community
Participate
Working Groups
The performance tests at https://hudson.eclipse.org/perftests/view/Eclipse%20and%20Equinox/ are still named starting with "ep45M" instead of "ep46M". The M-builds tell us there is a problem at the top of the page, where, for example, build http://download.eclipse.org/eclipse/downloads/drops4/M20160727-1700/ Says Invocation of Curl did not return 0 return code for ep46M-perf-lin64-baseline. return code was 22 Likely due to Hudson job not being defined (or, possibly network issues). While there are several things that can cause this message ... there really is no "ep46M" perf tests jobs defined. I think there was another bug for this ... not sure if it was closed for the 46N&I tests moving to 47N&I or if it is still open and we just never got around to the M-builds?
Sravan, want to take a crack? Remember, it goes easier if you go in "reverse" order. That is, rename the "last one" to run, then next to last one to run, .... ending with the first one to run. That way, the "next in the trigger chain" already exists and gets updated automatically. Otherwise, you will have two fields to change.
I've noticed a similar message for Y-builds: http://download.eclipse.org/eclipse/downloads/drops4/Y20160728-1000/ It appears they should be updated to ep47Y...
(In reply to David Williams from comment #1) > Sravan, want to take a crack? Remember, it goes easier if you go in > "reverse" order. That is, rename the "last one" to run, then next to last > one to run, .... ending with the first one to run. That way, the "next in > the trigger chain" already exists and gets updated automatically. Otherwise, > you will have two fields to change. Hi David, I tried to rename the jobs. It seems I donot have permission to rename these jobs. Can you please let me know the permission I need to get to edit these jobs? Sravan
(In reply to Sravan Kumar Lakkimsetti from comment #3) > (In reply to David Williams from comment #1) > > Sravan, want to take a crack? Remember, it goes easier if you go in > > "reverse" order. That is, rename the "last one" to run, then next to last > > one to run, .... ending with the first one to run. That way, the "next in > > the trigger chain" already exists and gets updated automatically. Otherwise, > > you will have two fields to change. > > Hi David, > > I tried to rename the jobs. It seems I donot have permission to rename these > jobs. Can you please let me know the permission I need to get to edit these > jobs? > > Sravan I just checked the permissions matrix is correct, but I bet it basically deletes one job (which you probably have permission for) and then creates a new job (which you probably do not have permission for). That needs to be done at a "system" level, and last time I tried, it did not work, due to that Hudson bug where cookies change values it should not. I have opened bug 498856 to give you "admin" rights to the performance machine.
Since bug 498856 is resolved, I assume this bug can be closed as well. Please reopen if necessary.
