Peter,
Thanks for getting that fixed. The associated patch has been removed so
we should be good now.
Jay
On 6/7/2018 9:15 AM, Peter Penchev wrote:
On Mon, Jun 04, 2018 at 02:40:09PM -0500, Sean McGinnis wrote:
Our CI has been chugging along since June 2nd (not really related to
the timin
On Mon, Jun 04, 2018 at 02:40:09PM -0500, Sean McGinnis wrote:
> >
> > Our CI has been chugging along since June 2nd (not really related to
> > the timing of your e-mail, it just so happened that we fixed another
> > small problem there). You can see the logs at
> >
> > http://logs.ci-openstac
>
> Our CI has been chugging along since June 2nd (not really related to
> the timing of your e-mail, it just so happened that we fixed another
> small problem there). You can see the logs at
>
> http://logs.ci-openstack.storpool.com/
>
Thanks Peter.
It looks like the reason the report run
Peter,
Thank you for the update. We are investigating why this shows up as
failing in our CI tracking list.
I will hold off on the associated patch.
Thank you for the quick response!
Jay
On 6/4/2018 2:07 PM, Peter Penchev wrote:
On Sat, Jun 02, 2018 at 06:13:23PM -0500, Jay S Bryant wrot
On Sat, Jun 02, 2018 at 06:13:23PM -0500, Jay S Bryant wrote:
> All,
>
> This note is to make everyone aware that I have submitted patches for a
> number of drivers that have not run 3rd party CI in 60 or more days. The
> following is a list of the drivers, how long since their CI last ran and
>
All,
This note is to make everyone aware that I have submitted patches for a
number of drivers that have not run 3rd party CI in 60 or more days.
The following is a list of the drivers, how long since their CI last ran
and links to the patches which mark them as unsupported drivers:
* Data
