dataset we could use to create a CI job to prevent
> regression.
>
> The script also deserves some sort of documentation regarding usage
> and debugging.
>
> Lastly, it would be usable outside of the log-gearman-worker environment.
>
>
Thanks for looking into this!
I would be h
5 tempest
> / \
> 6 foo 7 foo
>
> Would have the following jobs applied in order:
>
> 0 base, 1 devstack, 2 devstack, 3 tempest, 4 altbase,
> 5 tempest, 6 foo, 7 foo
>
We will need somewhere in the logs a description of the traversal that was
done to
d copy of build
> logic in the artifact release jobs.
>
Having the logic to pull logs in one place allows to have proper isolation
on the executor between logs coming from different nodes in multi-node
environments.
Andrea Frittoli (andreaf)
>
> Implementation
> ==
>
On Tue, Jul 11, 2017 at 9:46 PM Andreas Jaeger wrote:
> On 2017-07-11 21:39, David Moreau Simard wrote:
> > I don't want to sidetrack the thread but should someone also be taking
> > care of cleaning up stale branches in Devstack ?
> > It goes all the way back to kilo.
>
> Can we
Thanks for the upgrade, and for all the effort you folks put into keeping
our gerrit close to upstream!
One thing that I find inconvenient in the new UI is the size of the middle
(test results) column: it's too narrow, no matter how large my browser
window is, or what browser I use - which causes