[Starlingx-discuss] Sanity Results
Hello guys, During this week we are going to start sending Sanity results for each build. Until today , we have a Jenkins job called full-sanity-multinode-controller-2compute-horizon. As the name says, it is only for 1 controller, 2 compute configuration. We are facing some parsing issues that we need to investigate, the job is not showing the real values, blaming the robot plugin for Jenkins. Beside that we have a couple of test cases failing because of the execution order, this is almost done. Starting today, the job is triggered every time that a new ISO image is available. And will be alert in order to share those results, as I mention before, we are working on this job since it is going to be our baseline to determine if the ISO is healthy or not. https://starlingx-ci.ostc.intel.com/job/full-sanity-multinode-controller-2co... Please let me know who should I include on the Jenkins mail list that get this results. [cid:image001.png@01CF8BAC.3B4C5DD0] Martinez Monroy, Elio. QA Engineer. Open-source Technology Center
Hi Elio, Thanks for letting us know, please include this email list (starlingx-discuss@lists.starlingx.io) into the recipients for the report. It also would be good to know what tests are part of the Sanity check. BTW, the link you sent doesn't work in the open. Regards A. From: Martinez Monroy, Elio Sent: Monday, August 20, 2018 8:01 AM To: starlingx-discuss@lists.starlingx.io Cc: Cabrales, Ada <ada.cabrales@intel.com> Subject: Sanity Results Hello guys, During this week we are going to start sending Sanity results for each build. Until today , we have a Jenkins job called full-sanity-multinode-controller-2compute-horizon. As the name says, it is only for 1 controller, 2 compute configuration. We are facing some parsing issues that we need to investigate, the job is not showing the real values, blaming the robot plugin for Jenkins. Beside that we have a couple of test cases failing because of the execution order, this is almost done. Starting today, the job is triggered every time that a new ISO image is available. And will be alert in order to share those results, as I mention before, we are working on this job since it is going to be our baseline to determine if the ISO is healthy or not. https://starlingx-ci.ostc.intel.com/job/full-sanity-multinode-controller-2co... Please let me know who should I include on the Jenkins mail list that get this results. Martinez Monroy, Elio. QA Engineer. Open-source Technology Center
On Mon, Aug 20, 2018 at 4:23 PM, Cabrales, Ada <ada.cabrales@intel.com> wrote:
Thanks for letting us know, please include this email list (starlingx-discuss@lists.starlingx.io) into the recipients for the report.
If you do this (and I'm not saying it is a good or bad idea), please use a tag in the subject that makes it east to filter for those who may not want to see these emails. In general, sending automated email to a discussion list is rarely a popular idea. Also, they'll all be archived, which may or may not be a feature. This somewhat echos the conversation in IRC Friday about the Gerrit messages being more noise than signal. dt -- Dean Troyer dtroyer@gmail.com
participants (3)
-
Cabrales, Ada
-
Dean Troyer
-
Martinez Monroy, Elio