OK, I fixed the stable branch issue with this patch: https://git.opendaylight.org/gerrit/#/c/8130/ Now you have VTN coordinator test running on both branches. BR/Luis

OK, I fixed the stable branch issue with this patch: https://git.opendaylight.org/gerrit/#/c/8130/ Now you have VTN coordinator test running on both branches. BR/Luis

I think so, I checked and VTN coordinator in master runs on port 8083 so the test files you uploaded should be OK. However the VTN coordinator in stable/branch runs on port 8080 so the test file you

I think so, I checked and VTN coordinator in master runs on port 8083 so the test files you uploaded should be OK. However the VTN coordinator in stable/branch runs on port 8080 so the test file you

Hi Luis, Can we enable the Coordinator test cases now? Regards, Venkat G.

Hi Luis, Can we enable the Coordinator test cases now? Regards, Venkat G.

Thanks Andy, it works now. BR/Luis

Thanks Andy, it works now. BR/Luis

Hmm... apparently I still had some left over data from my initial testing and it had the wrong perms for you. I've cleared it out, try now. -- Andrew J Grimberg Systems Administrator The Linux

That worked but next issue here: https://jenkins.opendaylight.org/integration/job/integration-master-deploy-vtn-coordinator-latest/126/console BR/Luis

That worked but next issue here: https://jenkins.opendaylight.org/integration/job/integration-master-deploy-vtn-coordinator-latest/126/console BR/Luis

Ah, apparently I forgot to remove the sudo from the script. I've fixed the job so that it doesn't make unneeded sudo calls now. -Andy- -- Andrew J Grimberg Systems Administrator The Linux

I see this issue when I enable and fire the job: https://jenkins.opendaylight.org/integration/view/Deploy%20Jobs/job/integration-master-deploy-vtn-coordinator-latest/125/console BR/Luis

Hi all, As a result of yesterday test tasks discussion we have created following groups with the goal to work and deliver something by next milestone M3 (07/07/2014): 1) Infrastructure: 1.1)

Luis, The issue isn't how large the reports are, it's all the data that is pulled into all the various workspaces on the system. The workspaces don't get wiped at the end of a job but at the start.

Thanks Andy, Please take your time, I have other things to do anyway and devs are quiet so far. Just a comment: I have been checking and we have 24 robot jobs x 40 stored build reports = 960 robot

Thanks Andy, Please take your time, I have other things to do anyway and devs are quiet so far. Just a comment: I have been checking and we have 24 robot jobs x 40 stored build reports = 960 robot

Luis, I've fixed this but it looks like the system is running low in disk space. Given that artifacts aren't stored on that system (it's a slave) we're running into problems with how large the

Hi, Integration Robot VM is down. Could you please take a look? Thanks/Luis

Hi Rocky, thanks for the update. Gauges are nice and I also like the idea of plotting a dependency map based on project dependency declaration. BR/Luis