David Kranz writes:
> I just submitted https://review.openstack.org/#/c/11755/ to skip the
> tests that are failing. I filed three bug tickets too. I can only
> reproduce one of them in my environment (the one where the error code
> seems to have changed). BTW, I looked at the nova logs for a tem
JB> 1) We designed the devstack-gate with a facility to install the SSH
JB> key of the developer whose change failed onto the VM and give it to
JB> them for debugging purposes -- however, we've yet to have a
JB> devstack-gate node provider give us permission to hand out VMs like
JB> that. I'm sorr
Dan Smith writes:
> One thing I noticed while doing some of this was that Jenkins doesn't
> seem to know about dependent patches, and will often run them in some
> sub-optimal order. This means that if the third patch in a series of ten
> is broken, it still runs everything ten times, instead of
Thanks, Jim. It seems that the tests are passing after the submission to
skip some tests. That still leaves the problem of figuring out what the
problems are. I want to file a bug about the fact that there are
backtraces in the n-cpu log even on a "successful" build. I would
include a link to t
JB> * Dependent patch series are tested in the correct order (regardless of
JB> the order in which individual patches are approved, and patches are
JB> only queued for testing once all the patches ahead of them are
JB> approved). This eliminated a huge amount of churn, as you can
JB> imagi
Dan Smith writes:
> I just verified this by looking at the zuul queue link you provided. I
> see in the check queue things in the following order:
>
> 11411, 11500, 11823, 11754, 11440, 11351, 11353, 11482
Oh, I thought you were talking about gating; the check pipeline tests
patches independentl
JB> Oh, I thought you were talking about gating;
Well, I'm (incorrectly) using them interchangeably. I guess I better
stop that before someone gets hurt! :)
JB> the check pipeline tests patches independently, exactly as they are
JB> uploaded. So if you upload three dependent patches, it will run
David Kranz writes:
> Thanks, Jim. It seems that the tests are passing after the submission
> to skip some tests. That still leaves the problem of figuring out what
> the problems are. I want to file a bug about the fact that there are
> backtraces in the n-cpu log even on a "successful" build. I
8 matches
Mail list logo
