Hi Rohan, I have finally got time to go through the yang module pyang check issues you mentioned. I think for now the best we can do is to collect these errors and expose them in a jenkins job so proj

Hi everybody, I prepared this patch to run CSIT magnesium on JDK11: https://git.opendaylight.org/gerrit/#/c/releng/builder/+/84991/ However I have to warn that couple of CSITs I run on JDK11 failed du

Thanks Rohan (cc integration), Please send me the check.sh you are using for ODL so I can take a look and see how we can automate this check in ODL. As we discussed there is no point to push models to

Hi Karthika, to build a topic you just need to set the parameter PATCHES_TO_BUILD to topic=magnesium-mri (if you want to checkout first patch in the topic) or topic:magnesium-mri (if you want to cherr

It seems like this patch to update Multipatch job to openjdk11 did not work: https://git.opendaylight.org/gerrit/#/c/releng/builder/+/84868/1/jjb/integration/integration-test-jobs.yaml So now I am try

Yeah, something has changed recently so now AR jobs are failing almost immediately (so no CSIT is happening for the last 4 days): https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelea

It looks like robot tidy failed in the latest patch: robotframework tidy wrapper..............................................Failed Can you please pass the robot tidy tool to your robot code and upda

OK Mariusz, looking at your patch I still have couple of comments: 1) By default you do not want to run the CRUD-ACTION suite: For this you can move the new suite to new folder CRUD-ACTION: csit/suite

It is being long time we do not remove projects from AR/distribution, just remind the order is: - To remove: first distribution, second AR - To add: first AR, second distribution It is actually weird

Sorry for late response, see below: This is the CSIT verify job to check the new test code does not break existing test and it normally runs on a stable version of the controller (should be neon). The

I am not sure what is difference between your local env and ODL CI but yes the RPC is failing with 404 code even when using latest sodium code (I added job to sandbox): https://jenkins.opendaylight.or

I cannot see the ticket but this is same issue detected yesterday: https://lists.opendaylight.org/g/integration-dev/message/13697

Full log here: https://jenkins.opendaylight.org/releng/view/openflowplugin/job/netvirt-csit-3node-0cmb-1ctl-2cmp-openstack-queens-tempest-stateful-magnesium/25/console 09:45:52 ---> Create HEAT stack

Yes, this seems like a good KW to use. Also the CSIT is currently broken because a python missing dependency in the vexhost script: 09:45:54 No module named v1.contrib 09:45:54 Build step 'Execute she

Anil, FYI I tried to release using the new job but it failed, it worked in dry-run mode (1st build), but it failed when I set the build to publish (2nd build): https://jenkins.opendaylight.org/releng/

OK, lets go step by step, here: your patch runs this command in the mininet VM (where the testtool is deployed): /usr/lib/jvm/java-8-openjdk-amd64/bin/java -Xmx1G -XX:MaxPermSize=256M -jar netconf-tes

Sorry, yesterday I got distracted and forgot about this. I will try the release today before the integration call.

I just looked at the last build of the verify job and the issue seems to be the netconf testtool, unfortunately I cannot see the test tool log in the log server because you changed the line creating i

OK, I think this is the new job: https://jenkins.opendaylight.org/releng/view/distribution/job/distribution-release-merge/ Any doc explaining how to use it? BR/Luis

OK, I think I know what is going on: 'SSHLibrary.File Should Exist' searches the file in the remote system = mininet VM, I think you should use 'OperativeSystem.File Should Exist'. BR/Luis