Please ignore this message. I originally missed the email from Rudiger.

 

@Scott, please start tagging. From a load point of view, we are not waiting for anything.

 

Regards,

Ghada

 

From: Khalil, Ghada
Sent: Tuesday, August 04, 2020 9:31 AM
To: Scott Little <scott.little@windriver.com>; starlingx-discuss@lists.starlingx.io; Jascanu, Nicolae <nicolae.jascanu@intel.com>
Subject: RE: [Starlingx-discuss] No good images on July, 30 and 31

 

Hi Nick,

Can you confirm that the 4.0 built docker images were used in the latest sanity?  Did the openstack metrics test-cases pass with the newly built docker images?

 

Thanks,

Ghada

 

 

From: Scott Little [mailto:scott.little@windriver.com]
Sent: Friday, July 31, 2020 9:55 AM
To: starlingx-discuss@lists.starlingx.io
Subject: Re: [Starlingx-discuss] No good images on July, 30 and 31

 

I have triggered a forced build.

The last three scheduled builds detected no new package changes, and aborted the build without producing anything.  This is a bit of a problem if the prior container build build produced new docker images that need to be included in helm charts.  I'm looking at options to address this going forward.

Scott

 

On 2020-07-31 8:39 a.m., Jascanu, Nicolae wrote:

Hi All,

The sanity and metrics tests were NOT executed today because there is no proper image available:

http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/flock/20200730T173039Z/

http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/flock/20200730T214144Z/

http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/flock/20200731T070417Z/

 

Regards,

Nicolae Jascanu, Ph.D.

TSD Software Engineer

 

intel-logo

 

Internet Of Things Group

Galati, Romania

 

 

_______________________________________________
Starlingx-discuss mailing list
Starlingx-discuss@lists.starlingx.io
http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss