Thanks a lot for your quick replies Rudd, 1.We have Jenkins agent running on Orange pi, yeah our setup is configured in such a way that the DUT is connected to the Orange pi where Jenkins server is running on in Orange pi.
2.It is not possible to connect the DUT directly (as we don't have Jenkins server running on it) to the Jenkins without the orange pi, as this is how we have defined the test setup for triggering the plans like flashing to DUT and all etc., with orange pi board via specific Jenkins plan. 3.Yeah there is only one log.html for all these tests -- as all these tests are part of One jenkins plan ie., BIOS_settings_verification *4.By my problem is failure case robot framework reports are generated in DUT and not getting SCP'ed back to the tester board, whereas this works in case of success test log reports and are getting SCP'ed to tester board and getting updated in the Jenkins UI in the browser, but fails for failure log reports, not getting updated in Jenkins UI when opened in the browser and not getting SCP'ed back to the tester board, as it always still shows the old success log reports instead of showing the failure case reports in Jenkins UI in the browser even though when the job is failed as expected.* *5. I feel some Jenkins configuration is missing for logging the failure reports firstly on the Jenkins UI when opened in the browser. Could you please let me know if you have any idea like is there any configuration that is missing in Jenkins for logging failure case log reports running on orange pi?* Could you please let me know if you have any clues as am wandering from past 3 days still no clues yet. Many Thanks in advance On Mon, Nov 19, 2018 at 4:37 PM Ruud Prijs <[email protected]> wrote: > > > Hi > > I really wondering why you use a orange pi, is it not possible to connect > the dut directly to jenkins? > I also don't understand your issue, there is just one log file for all > tests, if you run test by test you should > give the log file a unique name for every run. in that case you can > better use xml and merge those output > files at the end of the run. and use in Jenkins the robot framework report > plugin. > > > > > > > Op za 17 nov. 2018 om 11:14 schreef srinivasan <[email protected]>: > >> Dear Jenkins /Robot framework community, >> >> As am newbie to Robot framework script and Jenkins, as my earlier >> expertise was in Embedded Linux development, my head is struggling one of >> the below issues in robot framework and jenkins as described below: >> >> *The setup is as below:* >> >> I have jenkins agent running in Orange Pi prime board (called as tester >> board), where I trigger the Jenkins plans via this Orange Pi prime >> board(tester board)(where the test code is downloaded in this tester board >> from git and copied to my DUT via SSH commands mentioned below to my final >> DUT and this is where the tests ie., robot framework scripts are being >> executed in the DUT) and the robot framemork logs/reports are collected >> back to this tester board from DUT. >> >> ********** Commands executed from Tester board to DUT via Jenkins Plan >> ********************************************************************************************************************************************************* >> >> #!/bin/bash >> >> ifconfig >> echo "Debugging for knowing the path" >> pwd >> mkdir /home/root/results >> whoami >> ls -l >> >> board_ip=$(cat /home/root/target_ip) >> scp -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -i >> ~/.ssh/id_rsa_dtfb -r qa/ root@${board_ip}:/home/root >> ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -i >> ~/.ssh/id_rsa_dtfb root@${board_ip} 'pip3 install robotframework' >> ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -i >> ~/.ssh/id_rsa_dtfb root@${board_ip} 'mkdir results' >> ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -i >> ~/.ssh/id_rsa_dtfb root@${board_ip} 'ls' >> ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -i >> ~/.ssh/id_rsa_dtfb root@${board_ip} 'python3 -m robot --outputdir >> results ~/qa/robot_tests/bios_settings_verification.robot' >> >> >> #!/bin/bash >> >> board_ip=$(cat /home/root/target_ip) >> scp -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -i >> ~/.ssh/id_rsa_dtfb -r root@${board_ip}:/home/root/results/ . >> sync >> ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -i >> ~/.ssh/id_rsa_dtfb root@${board_ip} 'rm -r /home/root/results' >> ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -i >> ~/.ssh/id_rsa_dtfb root@${board_ip} 'rm -r /home/root/qa' >> >> *********************************************************************************************************************************************************************************************************************************************** >> >> >> Logs: >> 15:14:05 [EnvInject] - Loading node environment variables. >> *15:14:05 Building remotely on PenguinTeam_OrangePI-Prime_2 >> (PenguinTeam-x86) in workspace >> /home/root/workspace/PenguinTeam/BIOS_settings_verification* >> 15:14:05 > git rev-parse --is-inside-work-tree # timeout=10 >> 15:14:05 Fetching changes from the remote Git repository >> 15:14:05 > git config remote.origin.url >> https://bitbucket.bln.native-instruments.de/scm/emb/qa.git # timeout=10 >> 15:14:05 Fetching upstream changes from >> https://bitbucket.bln.native-instruments.de/scm/emb/qa.git >> 15:14:05 > git --version # timeout=10 >> 15:14:05 using GIT_ASKPASS to set credentials UsernamePassword >> 15:14:05 > git fetch --tags --progress >> https://bitbucket.bln.native-instruments.de/scm/emb/qa.git >> +refs/heads/*:refs/remotes/origin/* >> 15:14:05 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10 >> 15:14:05 > git rev-parse refs/remotes/origin/origin/master^{commit} # >> timeout=10 >> 15:14:06 Checking out Revision 594cc81aa291f1e9f0730d8476d129592e792f28 >> (refs/remotes/origin/master) >> 15:14:06 > git config core.sparsecheckout # timeout=10 >> 15:14:06 > git checkout -f 594cc81aa291f1e9f0730d8476d129592e792f28 >> 15:14:06 Commit message: "Updated Thomas review comments" >> 15:14:06 > git rev-list --no-walk >> 594cc81aa291f1e9f0730d8476d129592e792f28 # timeout=10 >> 15:14:06 [BIOS_settings_verification] $ /bin/bash >> /tmp/jenkins8191990223406863240.sh >> 15:14:06 docker0 Link encap:Ethernet HWaddr 02:42:0B:8D:B2:4B >> 15:14:06 inet addr:172.17.0.1 Bcast:172.17.255.255 >> Mask:255.255.0.0 >> 15:14:06 UP BROADCAST MULTICAST MTU:1500 Metric:1 >> 15:14:06 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 >> 15:14:06 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 >> 15:14:06 collisions:0 txqueuelen:0 >> 15:14:06 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) >> 15:14:06 >> 15:14:06 eth0 Link encap:Ethernet HWaddr 02:01:E4:1C:3E:33 >> 15:14:06 inet addr:10.1.9.51 Bcast:10.1.11.255 >> Mask:255.255.252.0 >> 15:14:06 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> 15:14:06 RX packets:4793744 errors:0 dropped:860 overruns:0 >> frame:0 >> 15:14:06 TX packets:818823 errors:0 dropped:0 overruns:0 >> carrier:0 >> 15:14:06 collisions:0 txqueuelen:1000 >> 15:14:06 RX bytes:1046531973 (998.0 MiB) TX bytes:544566075 >> (519.3 MiB) >> 15:14:06 Interrupt:25 >> 15:14:06 >> 15:14:06 lo Link encap:Local Loopback >> 15:14:06 inet addr:127.0.0.1 Mask:255.0.0.0 >> 15:14:06 UP LOOPBACK RUNNING MTU:65536 Metric:1 >> 15:14:06 RX packets:149 errors:0 dropped:0 overruns:0 frame:0 >> 15:14:06 TX packets:149 errors:0 dropped:0 overruns:0 carrier:0 >> 15:14:06 collisions:0 txqueuelen:1000 >> 15:14:06 RX bytes:16640 (16.2 KiB) TX bytes:16640 (16.2 KiB) >> 15:14:06 >> 15:14:06 Debugging for knowing the path >> 15:14:06 /home/root/workspace/PenguinTeam/BIOS_settings_verification >> 15:14:06 mkdir: can't create directory '/home/root/results': File exists >> 15:14:06 root >> 15:14:06 total 12 >> 15:14:06 drwxr-xr-x 9 root root 4096 Nov 9 08:36 qa >> 15:14:06 drwxr-xr-x 2 root root 4096 Nov 16 14:14 qa@tmp >> 15:14:06 drwxr-xr-x 2 root root 4096 Nov 16 12:13 results >> 15:14:06 Warning: Permanently added '10.1.9.37' (RSA) to the list of >> known hosts. >> 15:14:07 Warning: Permanently added '10.1.9.37' (RSA) to the list of >> known hosts. >> 15:14:09 Requirement already satisfied: robotframework in >> /usr/lib/python3.5/site-packages >> 15:14:09 You are using pip version 9.0.2, however version 18.1 is >> available. >> 15:14:09 You should consider upgrading via the 'pip install --upgrade >> pip' command. >> 15:14:09 Warning: Permanently added '10.1.9.37' (RSA) to the list of >> known hosts. >> 15:14:09 mkdir: cannot create directory 'results': File exists >> 15:14:10 Warning: Permanently added '10.1.9.37' (RSA) to the list of >> known hosts. >> 15:14:10 qa >> 15:14:10 results >> 15:14:10 speedtest >> 15:14:10 Warning: Permanently added '10.1.9.37' (RSA) to the list of >> known hosts. >> 15:14:10 >> ============================================================================== >> 15:14:10 Bios Settings Verification :: This is the Maschine Native OS >> BIOS settings ... >> 15:14:10 >> ============================================================================== >> *15:14:10 Verify Backup Map file BIOS settings >> | FAIL |* >> *15:14:11 'False' should be true.* >> *15:14:11 >> ------------------------------------------------------------------------------* >> *15:14:11 Verify Default Map file BIOS settings >> | PASS |* >> *15:14:12 >> ------------------------------------------------------------------------------* >> *15:14:12 Bios Settings Verification :: This is the Maschine Native OS >> BIOS ... | FAIL |* >> *15:14:12 2 critical tests, 1 passed, 1 failed* >> *15:14:12 2 tests total, 1 passed, 1 failed* >> 15:14:12 >> ============================================================================== >> *15:14:12 Output: /home/root/results/output.xml* >> *15:14:12 Log: /home/root/results/log.html* >> *15:14:12 Report: /home/root/results/report.html* >> 15:14:12 Build step 'Execute shell' marked build as failure >> 15:14:12 Robot results publisher started... >> 15:14:12 -Parsing output xml: >> 15:14:12 Done! >> 15:14:12 -Copying log files to build dir: >> 15:14:12 Done! >> 15:14:12 -Assigning results to build: >> 15:14:13 Done! >> 15:14:13 -Checking thresholds: >> 15:14:13 Done! >> 15:14:13 Done publishing Robot results. >> 15:14:13 [BFA] Scanning build for known causes... >> 15:14:13 [BFA] No failure causes found >> 15:14:13 [BFA] Done. 0s >> 15:14:13 Finished: FAILURE >> >> *The issue is as below:* >> >> *In my Jenkins plans, for the success case scenarios, I see the logs are >> getting generated in the DUT and collected to the tester board via SSH in >> Jenkins, but for failure case scenarios (ie., even though I can see the job >> failing in jenkins, but w.r.t the reports/logs, it still shows the earlier >> successfully passed reports in the Jenkins UI browser instead of showing >> the number of failed test cases reports in the Jenkins UI), And eventhough >> the failure case scenarios logs are successfully generated with the number >> of test cases failed in the DUT, these logs are not getting copied back to >> the tester board via SSH and not being updated in the Jenkins UI or >> browser. But for the success case scenarios the below commands works fine >> and logs getting in the Jenkins UI or browser* >> >> *#!/bin/bash* >> >> *board_ip=$(cat /home/root/target_ip)* >> *scp -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -i >> ~/.ssh/id_rsa_dtfb -r root@${board_ip}:/home/root/results/ .* >> *sync* >> *ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -i >> ~/.ssh/id_rsa_dtfb root@${board_ip} 'rm -r /home/root/results'* >> *ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -i >> ~/.ssh/id_rsa_dtfb root@${board_ip} 'rm -r /home/root/qa'* >> >> *the logs are in the (DUT) - ssh [email protected] <[email protected]>) ---> >> /home/root/results/log.html --> these failure logs are not getting scp to >> the tester board (* >> *ssh [email protected] <[email protected]>) to the path >> "/home/root/workspace/PenguinTeam/BIOS_settings_verification/results"* >> >> *The robot script is executed on DUT and results are copied back to the >> tester board.* >> >> *I hope once I collect successfully the failure logs in the tester board >> , the failure reports might get successfully updated in the Jenkins UI in >> the browser.* >> >> *Could you please help me in resolving the issue in Jenkins, finally why >> am unable to collect the logs for the failure case scenarios to the tester >> baord from Jenkins.* >> >> *I have hereby attached the robot script, screenshots of Jenkins Plans in >> the UI int he browser and the failure case reports/logs thats not getting >> copied to the tester board, please let me know if you require any other >> info w.r.t the issue for providing me the inputs* >> >> *If this is not the right place, please redirect me to the correct mail >> ids where I can post this issues, as am stuck with this issue for more than >> 2 days* >> >> *Many Thanks in advance,* >> >> -- >> You received this message because you are subscribed to the Google Groups >> "robotframework-users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to >> [email protected]. >> Visit this group at https://groups.google.com/group/robotframework-users. >> For more options, visit https://groups.google.com/d/optout. >> > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAFsTbWds7%3D4qWqstUyWC0bSzJjKzTsOPFz16m%3D-HTPj3ep2E_A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
