On Sat, May 03, 2014 at 07:41:54AM +, Kenichi Oomichi wrote:
Hi Matthew,
-Original Message-
From: Matthew Treinish [mailto:mtrein...@kortar.org]
Sent: Friday, May 02, 2014 12:36 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack
Just a quick reminder that the weekly OpenStack QA team IRC meeting will be
this Thursday, May 22nd at 17:00 UTC in the #openstack-meeting channel. I'm
sending the reminder out a little earlier this week because the usual meeting
cadence was interrupted by the off week and summit.
The agenda for
Hi Everyone,
So I was preparing to push the first tag as part of the move to a world with a
branchless tempest and was trying to figure out the naming convention we should
be using. The only complexity here is that we are targeting to do 4 releases a
year that coincide with the OpenStack
On Fri, May 23, 2014 at 01:01:42AM +, Jeremy Stanley wrote:
On 2014-05-22 20:40:16 -0400 (-0400), Sean Dague wrote:
Given that we're not really going to have major / minor bumps at this
point (more a continous roll), I might argue that we should just go
Firefox on it and bump the
Hi Everyone,
As part of moving to the new blueprint review process with the qa-specs repo [1]
I'm going to do a purge of the current tempest blueprint list. I'm planning to
do this next Thursday, the 29th, sometime before the QA meeting. This is really
just an exercise to cleanup and prioritize
Just a quick reminder that the weekly OpenStack QA team IRC meeting will be
tomorrow Thursday, May 29th at 22:00 UTC in the #openstack-meeting channel.
The agenda for tomorrow's meeting can be found here:
https://wiki.openstack.org/wiki/Meetings/QATeamMeeting
Anyone is welcome to add an item to
Hi Everyone,
So we'd like to announce to everyone that we're going to be doing a combined
Infra and QA program mid-cycle meet-up. It will be the week of July 14th in
Darmstadt, Germany at Deutsche Telekom who has graciously offered to sponsor the
event. The plan is to use the week as both a time
On Mon, Jun 02, 2014 at 06:57:04AM -0400, Sean Dague wrote:
Towards the end of the summit there was a discussion about us using a
shared review dashboard to see if a common view by the team would help
accelerate people looking at certain things. I spent some time this
weekend working on a tool
Hi Everyone,
Just a quick reminder that the weekly OpenStack QA team IRC meeting will be
this Thursday, June 5th at 17:00 UTC in the #openstack-meeting channel.
The agenda for tomorrow's meeting can be found here:
https://wiki.openstack.org/wiki/Meetings/QATeamMeeting
Anyone is welcome to add an
On Thu, May 29, 2014 at 12:07:07PM -0400, Matthew Treinish wrote:
Hi Everyone,
So we'd like to announce to everyone that we're going to be doing a combined
Infra and QA program mid-cycle meet-up. It will be the week of July 14th in
Darmstadt, Germany at Deutsche Telekom who has graciously
Hi Josh,
Just a heads up that you shouldn't use this list for any discussion. We've moved
all of the discussion off this list into openstack-dev. The only reason we
haven't removed the openstack-qa list is so we have a separate address for the
periodic job results. (which honestly hasn't been the
Hi everyone,
Just a quick reminder that the weekly OpenStack QA team IRC meeting will be
tomorrow Thursday, October 2nd at 22:00 UTC in the #openstack-meeting
channel.
The agenda for tomorrow's meeting can be found here:
https://wiki.openstack.org/wiki/Meetings/QATeamMeeting
Anyone is welcome to
On Tue, Oct 07, 2014 at 04:28:23PM +0100, Chris Dent wrote:
On Mon, 25 Aug 2014, Joe Gordon wrote:
On Mon, Aug 4, 2014 at 3:29 AM, Chris Dent chd...@redhat.com wrote:
For constraints: Will tempest be available as a stable library? Is using
tempest (or other same library across all projects) a
Hi Everyone,
As we are moving into the kilo cycle and now that DepFreeze has ended the door
has been opened for adding tempest-lib to the requirements list:
https://review.openstack.org/122478
Once that lands we'll be able to start using tempest-lib in projects. The first
use for tempest-lib
Hi Everyone,
Just a quick reminder that the weekly OpenStack QA team IRC meeting will be
this Thursday, October 9th at 17:00 UTC in the #openstack-meeting channel.
The agenda for tomorrow's meeting can be found here:
https://wiki.openstack.org/wiki/Meetings/QATeamMeeting
Anyone is welcome to add
Hi everyone,
Just a quick reminder that the weekly OpenStack QA team IRC meeting will be
tomorrow Thursday, October 16th at 22:00 UTC in the #openstack-meeting
channel.
The agenda for tomorrow's meeting can be found here:
https://wiki.openstack.org/wiki/Meetings/QATeamMeeting
Anyone is welcome
On Tue, Oct 21, 2014 at 08:09:38PM -0400, Davanum Srinivas wrote:
Hi all,
On the cross project meeting today, i promised to bring this to the
ML[1]. So here it is:
Question : Can a StackForge project (like nova-docker), depend on a
library (docker-py) that is not specified in global
Hi Everyone,
Just a quick reminder that the weekly OpenStack QA team IRC meeting will be
this Thursday, October 23rd at 17:00 UTC in the #openstack-meeting channel.
The agenda for tomorrow's meeting can be found here:
https://wiki.openstack.org/wiki/Meetings/QATeamMeeting
Anyone is welcome to
Hi everyone,
Just a quick reminder that the weekly OpenStack QA team IRC meeting will be
tomorrow Thursday, October 30th at 22:00 UTC in the #openstack-meeting
channel.
The agenda for tomorrow's meeting can be found here:
https://wiki.openstack.org/wiki/Meetings/QATeamMeeting
Anyone is welcome
Hi everyone,
Before we start the larger discussion at summit next week about the future of
testing in OpenStack - specifically about spinning up functional testing and how
it relates to tempest - I would like to share some of my thoughts on how we can
get things started and how I think they'll
On Mon, Nov 17, 2014 at 08:24:47AM -0500, Davanum Srinivas wrote:
Sean, Joe, Dean, all,
Here's the Nova change to disable the V2 XML support:
https://review.openstack.org/#/c/134332/
To keep all the jobs happy, we'll need changes in tempest, devstack,
devstack-gate as well:
Tempest :
on the Tempest review saying it's
got Nova core sign off with the link. (it's just procedural, I know that
everyone wants to kill the XML API, myself included)
-Matt Treinish
On Mon, Nov 17, 2014 at 8:48 AM, Matthew Treinish mtrein...@kortar.org
wrote:
On Mon, Nov 17, 2014 at 08:24:47AM -0500, Davanum
On Tue, Nov 18, 2014 at 06:29:55PM +0400, Boris Pavlovic wrote:
Hi stackers,
As far as you maybe know Rally has rally verify command that simplifies
usage of tempest.
We are testing this functionality in our gates on every patch (for about
month).
Everything was fine until today when
Hi everyone,
Just a quick reminder that the weekly OpenStack QA team IRC meeting will be
tomorrow Thursday, November 20th at 17:00 UTC in the #openstack-meeting
channel.
The agenda for tomorrow's meeting can be found here:
https://wiki.openstack.org/wiki/Meetings/QATeamMeeting
Anyone is welcome
Hi everyone,
Earlier today https://review.openstack.org/136017 merged which adds stable
compat jobs to most of the oslo libraries. This was done in reaction to 2
separate incidents in the past 2 days where both oslo.vmware and taskflow landed
changes that added new requirements which weren't in
On Fri, Nov 21, 2014 at 09:20:40AM -0500, Doug Hellmann wrote:
On Nov 20, 2014, at 4:39 PM, Matthew Treinish mtrein...@kortar.org wrote:
Hi everyone,
Earlier today https://review.openstack.org/136017 merged which adds stable
compat jobs to most of the oslo libraries. This was done
Hi Everyone,
I'd like to propose we add Ghanshyam Mann (gmann) to the tempest core team. Over
the past couple of cycles Ghanshyam has been actively engaged in the Tempest
community. Ghanshyam has had one of the highest review counts on Tempest for
the past cycle, and he has consistently been
On Fri, Nov 21, 2014 at 10:30:59AM -0800, Joe Gordon wrote:
On Fri, Nov 21, 2014 at 8:57 AM, Sahid Orentino Ferdjaoui
sahid.ferdja...@redhat.com wrote:
On Thu, Nov 20, 2014 at 02:00:11PM -0800, Joe Gordon wrote:
On Thu, Nov 20, 2014 at 9:49 AM, Sahid Orentino Ferdjaoui
On Fri, Nov 21, 2014 at 04:15:07PM -0500, Sean Dague wrote:
On 11/21/2014 01:52 PM, Matthew Treinish wrote:
On Fri, Nov 21, 2014 at 07:15:49PM +0100, jordan pittier wrote:
Hey,
I am not a Nova developer but I still have an opinion.
Using boolean assertions
I like what you propose. We
On Tue, Nov 25, 2014 at 10:03:41AM -0500, Sean Dague wrote:
As we are trying to do smart disaggregation of tests in the gate, I
think it's important to figure out which test configurations seem to be
actually helping, and which aren't. As the swift team has long had a
functional test job, this
On Tue, Nov 25, 2014 at 11:01:04AM -0500, Sean Dague wrote:
On 11/25/2014 10:54 AM, Matthew Treinish wrote:
On Tue, Nov 25, 2014 at 10:03:41AM -0500, Sean Dague wrote:
As we are trying to do smart disaggregation of tests in the gate, I
think it's important to figure out which test
On Mon, Nov 24, 2014 at 10:49:27AM +0100, Angelo Matarazzo wrote:
Sorry for my previous message with wrong subject
Hi all,
By reading the tempest documentation page [1] a user can run tempest tests
by using whether testr or run_tempest.sh or tox.
What is the best practice?
run_tempest.sh
On Tue, Nov 25, 2014 at 01:22:01PM -0800, Vishvananda Ishaya wrote:
On Nov 25, 2014, at 7:29 AM, Matt Riedemann mrie...@linux.vnet.ibm.com
wrote:
On 11/25/2014 9:03 AM, Matt Riedemann wrote:
On 11/25/2014 8:11 AM, Sean Dague wrote:
There is currently a review stream coming
andrea.fritt...@gmail.com :
+1
On 21 Nov 2014 18:25, Ken1 Ohmichi ken1ohmi...@gmail.com wrote:
+1 :-)
Sent from my iPod
On 2014/11/22, at 7:56, Christopher Yeoh cbky...@gmail.com wrote:
+1
Sent from my iPad
On 22 Nov 2014, at 4:56 am, Matthew Treinish
Hi Everyone,
I figured I'd send a quick announcement that we won't be having a meeting this
week. The next meeting will be next week, Dec. 4th at 17:00 UTC.
Thanks,
-Matt Treinish
pgpCJ2s1V0P2N.pgp
Description: PGP signature
___
OpenStack-dev
On Thu, Jul 25, 2013 at 10:16:54AM +0930, Christopher Yeoh wrote:
On Wed, 24 Jul 2013 10:22:32 -0400
Matthew Treinish mtrein...@kortar.org wrote:
On Wed, Jul 24, 2013 at 10:48:19PM +0930, Christopher Yeoh wrote:
On Wed, 24 Jul 2013 21:08:03 +0800
Zhu Bo bo...@linux.vnet.ibm.com wrote
On Wed, Aug 14, 2013 at 11:05:35AM -0500, Ben Nemec wrote:
On 2013-08-13 16:39, Clark Boylan wrote:
On Tue, Aug 13, 2013 at 1:25 PM, Matthew Treinish
mtrein...@kortar.org wrote:
Hi everyone,
So for the past month or so I've been working on getting tempest
to work stably
with testr
On Fri, Aug 16, 2013 at 01:03:57PM -0500, Ben Nemec wrote:
Getting this in before the H3 rush would be very helpful. When we made
the switch with Nova's unittests we fixed as many of the test bugs
that we could find, merged the change to switch the test runner, then
treated all failures as
On Wed, Aug 14, 2013 at 06:13:18PM -0300, Thierry Carrez wrote:
Matthew Treinish wrote:
Also, if anyone has any input on what threshold they feel is good enough
for this I'd welcome any input on that. For example, do we want to ensure
a = 1:1 match for job success? Or would something like
On Thu, Aug 22, 2013 at 04:36:18PM -0500, Ben Nemec wrote:
On 2013-08-22 16:28, Matthew Treinish wrote:
Another option that I've thought about is making the testr-full
jobs voting on
the check queue. This way it will raise parallel failures to
peoples attention
but not increase the number
Hi everyone,
So as the title indicates I pushed through the change that migrates tempest to
run by default in parallel. (except for the neutron job, which still needs work
to run in parallel) This should improve the run times for tempest jobs to
between 20-30min on average which will definitely
+1 for both of them. They've both done great work.
-Matt Treinish
On Wed, Sep 11, 2013 at 04:32:11PM -0400, Sean Dague wrote:
We're in Feature Freeze for the Open Stack projects, which actually
means we're starting the busy cycle for Tempest in people landing
additional tests for verification
On Fri, Aug 30, 2013 at 12:23:03PM -0400, David Kranz wrote:
Now that we have achieved the goal of parallel tempest in the gate
using testr we have to be careful that we don't introduce tests that
are flaky. This may be obvious to many of you but we should include
some information in the
On Wed, Dec 03, 2014 at 09:43:41AM -0500, David Kranz wrote:
A recent proposed test to tempest was making explicit calls to the nova
extension discovery api rather than using test.requires_ext. The reason was
because we configure tempest.conf in the gate as 'all' for extensions, and
the test
Hi everyone,
Just a quick reminder that the weekly OpenStack QA team IRC meeting will be
tomorrow Thursday, December 4th at 17:00 UTC in the #openstack-meeting
channel.
The agenda for tomorrow's meeting can be found here:
https://wiki.openstack.org/wiki/Meetings/QATeamMeeting
Anyone is welcome
On Tue, Dec 09, 2014 at 10:15:34AM -0600, Brian Curtin wrote:
On Tue, Dec 9, 2014 at 9:05 AM, Sean Dague s...@dague.net wrote:
- [H305 H306 H307] Organize your imports according to the `Import order
template`_ and `Real-world Import Order Examples`_ below.
I think these remain
Hi everyone,
Just a quick reminder that the weekly OpenStack QA team IRC meeting will be
tomorrow Thursday, December 11th at 22:00 UTC in the #openstack-meeting
channel.
The agenda for tomorrow's meeting can be found here:
https://wiki.openstack.org/wiki/Meetings/QATeamMeeting
Anyone is welcome
Hi everyone,
Just a quick reminder that the weekly OpenStack QA team IRC meeting will be
tomorrow Thursday, December 18th at 17:00 UTC in the #openstack-meeting
channel.
The agenda for tomorrow's meeting can be found here:
https://wiki.openstack.org/wiki/Meetings/QATeamMeeting
Anyone is welcome
Just a quick reminder that the weekly OpenStack QA team IRC meeting will be
tomorrow Thursday, February 5th at 22:00 UTC in the #openstack-meeting
channel.
The agenda for tomorrow's meeting can be found here:
https://wiki.openstack.org/wiki/Meetings/QATeamMeeting
Anyone is welcome to add an item
On Mon, Feb 02, 2015 at 11:46:53AM -0600, Matt Riedemann wrote:
This came up in the operators mailing list back in June [1] but given the
subject probably didn't get much attention.
Basically there is a really old bug [2] from Grizzly that is still a problem
and affects multiple projects. A
On Mon, Feb 02, 2015 at 07:35:46PM +0300, Alexandre Levine wrote:
Thank you Sean.
We'll be tons of EC2 Tempest tests for your attention shortly.
How would you prefer them? In several reviews, I believe. Not in one, right?
Let's take a step back for a sec. How many tests and what kind are we
On Mon, Feb 02, 2015 at 11:49:26AM -0600, Chris Friesen wrote:
On 02/02/2015 10:51 AM, Jay Pipes wrote:
This is a bug that I discovered when fixing some of the NUMA related nova
objects. I have a patch that should fix it up shortly.
Any chance you could point me at it or send it to me?
On Mon, Feb 02, 2015 at 08:07:27PM +0300, Alexandre Levine wrote:
On 2/2/15 7:39 PM, Sean Dague wrote:
On 02/02/2015 11:35 AM, Alexandre Levine wrote:
Thank you Sean.
We'll be tons of EC2 Tempest tests for your attention shortly.
How would you prefer them? In several reviews, I believe.
On Wed, Jan 21, 2015 at 11:20:12AM +0900, Ken'ichi Ohmichi wrote:
Hi David,
As we told today, I tried Neutron service client migration to tempest-lib.
but I found some blocking thing for it and I'd like to share it.
I thought that the base service_client module and neutron service client
on making
sure the gating machinery stays well oiled and doesn't breakdown.
[1] https://etherpad.openstack.org/p/stable-tracker
Matthew Treinish wrote:
So I think it's time we called the icehouse branch and marked it EOL. We
originally conditioned the longer support window on extra people
Hi everyone,
Just a quick reminder that the weekly OpenStack QA team IRC meeting will be
tomorrow Thursday, February 12th at 17:00 UTC in the #openstack-meeting
channel.
The agenda for tomorrow's meeting can be found here:
https://wiki.openstack.org/wiki/Meetings/QATeamMeeting
Anyone is welcome
On Tue, Feb 10, 2015 at 11:50:28AM -0500, David Kranz wrote:
On 02/10/2015 10:35 AM, Matthew Treinish wrote:
On Tue, Feb 10, 2015 at 11:19:20AM +0100, Thierry Carrez wrote:
Joe, Matt Matthew:
I hear your frustration with broken stable branches. With my
vulnerability management team member
Hi everyone,
Just a quick reminder that the weekly OpenStack QA team IRC meeting will be
tomorrow Thursday, February 19th at 22:00 UTC in the #openstack-meeting
channel.
The agenda for tomorrow's meeting can be found here:
https://wiki.openstack.org/wiki/Meetings/QATeamMeeting
Anyone is welcome
space is limited to 10 seats. So if you're not going to be
directly involved in any of the work items for this sprint I'd ask that you
please be mindful of that before registering to attend.
Thanks,
Matthew Treinish
pgpokPu31O4Qx.pgp
Description: PGP signature
Hi Everyone,
Just wanted to send out an announcement that there will be no QA meeting this
week. The next QA meeting will be next weeks on Thurs. Feb. 5th at 2200 UTC.
Thanks,
Matt Treinish
pgpVKXJEVfoUP.pgp
Description: PGP signature
On Mon, Feb 09, 2015 at 01:24:34PM -0600, Matt Riedemann wrote:
On 2/9/2015 12:23 PM, Joe Gordon wrote:
On Feb 9, 2015 10:04 AM, Matt Riedemann mrie...@linux.vnet.ibm.com
mailto:mrie...@linux.vnet.ibm.com wrote:
There are at least two blocking bugs:
1.
On Mon, Feb 09, 2015 at 03:10:28PM -0600, Matt Riedemann wrote:
On 2/9/2015 2:56 PM, Matthew Treinish wrote:
On Mon, Feb 09, 2015 at 01:24:34PM -0600, Matt Riedemann wrote:
On 2/9/2015 12:23 PM, Joe Gordon wrote:
On Feb 9, 2015 10:04 AM, Matt Riedemann mrie...@linux.vnet.ibm.com
Hi everyone,
Just a quick reminder that the weekly OpenStack QA team IRC meeting will be
tomorrow Thursday, March 19th at 22:00 UTC in the #openstack-meeting
channel.
The agenda for tomorrow's meeting can be found here:
https://wiki.openstack.org/wiki/Meetings/QATeamMeeting
Anyone is welcome to
On Mon, Mar 09, 2015 at 10:47:21AM -0400, Attila Fazekas wrote:
Hi All,
This is follow up on [1].
Running the full tempest test-suite in parallel without the
allow_tenant_isolation=True settings, can cause random not too obvious
failures, which caused lot of issue to tempest newcomers.
On Mon, Mar 09, 2015 at 09:52:54AM -0400, David Kranz wrote:
Since test_server_cfn_init was recently moved from tempest to the heat
functional tests, there are no subclasses of OrchestrationScenarioTest.
If there is no plan to add any more heat scenario tests to tempest I would
like to remove
Hi Everyone,
I just wanted to mention that in the past couple of weeks we've started an
effort to write some documentation to explain common aspects of tempest
configuration. The current version of the doc can be found here:
http://docs.openstack.org/developer/tempest/configuration.html
Right
Hi everyone,
Just a quick reminder that the weekly OpenStack QA team IRC meeting will be
tomorrow Thursday, March 12th at 17:00 UTC in the #openstack-meeting
channel.
The agenda for tomorrow's meeting can be found here:
https://wiki.openstack.org/wiki/Meetings/QATeamMeeting
Anyone is welcome to
On Mon, Mar 30, 2015 at 12:21:18PM +0530, Rohan Kanade wrote:
Since tests can now be removed from Tempest
https://wiki.openstack.org/wiki/QA/Tempest-test-removal and migrated to
their specific projects.
Does Tempest plan to discover/run these tests in tempest gates? If yes, how
is that
Hi Everyone,
I started an etherpad to begin planning and brainstorming ideas for summit
sessions here:
https://etherpad.openstack.org/p/liberty-qa-summit-topics
Feel free to add on it to it if you have an idea for a session.
Thanks,
-Matt Treinish
pgpQE7CeD5ee1.pgp
Description: PGP
Hi everyone,
Just a quick reminder that the weekly OpenStack QA team IRC meeting will be
Thursday, March 5th at 22:00 UTC in the #openstack-meeting channel.
The agenda for the meeting can be found here:
https://wiki.openstack.org/wiki/Meetings/QATeamMeeting
Anyone is welcome to add an item to
Hi everyone,
Just a quick reminder that the weekly OpenStack QA team IRC meeting will be
tomorrow Thursday, February 26th at 17:00 UTC in the #openstack-meeting
channel.
The agenda for tomorrow's meeting can be found here:
https://wiki.openstack.org/wiki/Meetings/QATeamMeeting
Anyone is welcome
Hi Everyone,
There will be no QA meeting this week/today because a large contingent of
people are
at the QA code sprint this week. We will have the meeting next Thurs. at 22:00
UTC.
Thanks,
Matt Treinish
pgpwbqXGouzlB.pgp
Description: PGP signature
Hi Everyone,
I'd like to throw my hat into the ring for another cycle as the PTL for the QA
program/team/group/whatever it's called under the new governance model.
This past cycle has been a very exciting one for the QA program. We've made a
bunch of progress on numerous work items to improve
On Thu, Apr 09, 2015 at 11:05:10AM +0900, Ken'ichi Ohmichi wrote:
2015-04-09 4:14 GMT+09:00 Sean Dague s...@dague.net:
On 04/08/2015 02:58 PM, David Kranz wrote:
On 04/08/2015 02:36 PM, Matthew Treinish wrote:
On Wed, Apr 08, 2015 at 01:08:03PM -0400, David Kranz wrote:
Since tempest
On Mon, Apr 20, 2015 at 03:10:40PM -0700, Ian Wells wrote:
On 20 April 2015 at 13:02, Kevin L. Mitchell kevin.mitch...@rackspace.com
wrote:
On Mon, 2015-04-20 at 13:57 -0600, Chris Friesen wrote:
However, minor changes like that could still possibly break clients
that are not
On Wed, Apr 22, 2015 at 02:03:13PM -0400, Emilien Macchi wrote:
On 04/22/2015 11:53 AM, Spencer Krum wrote:
Emillen,
Do you see shelling out to openstackclient in the keystone test to
verify that the keystone resources have been created? Do you see trying
to hit the api from
Hi everyone,
Just a quick reminder that the weekly OpenStack QA team IRC meeting will be
tomorrow Thursday, April 23rd at 17:00 UTC in the #openstack-meeting channel.
The agenda for tomorrow's meeting can be found here:
https://wiki.openstack.org/wiki/Meetings/QATeamMeeting
Anyone is welcome to
On Tue, Apr 28, 2015 at 02:21:27PM +0300, Yaroslav Lobankov wrote:
Guys, thank you for answers!
Then I have one more question :) How do scenario tests (that establish SSH
connection to instances) work?
So the scenario tests don't use the run_ssh flag, they just ssh in to servers
when they
On Thu, Apr 30, 2015 at 05:44:40PM +0100, Louis Taylor wrote:
On Thu, Apr 30, 2015 at 12:28:15PM -0400, Matthew Treinish wrote:
We're now at the end of the cycle and there are 3 clients that still have
CLI
tests in tempest. I have pushed the patch up to remove all these tests here
Hi Everyone,
At the beginning of the cycle I said by the end of the cycle I wanted to remove
all the python-*client CLI tests from tempest since they really weren't in the
scope of the project and the framework for cli testing was the first thing
included in tempest-lib. [1]
Additionally a
On Mon, May 04, 2015 at 10:05:03PM +0800, Yu Xing YX Wang wrote:
Hi,
I have a review(https://review.openstack.org/#/c/178561/) which is depend
on another review(https://review.openstack.org/#/c/178546/)
This Depends-On makes the first review's build failure. who can help me
resolve it?
Hi everyone,
Just a quick reminder that the weekly OpenStack QA team IRC meeting will be
tomorrow Thursday, April 16th at 22:00 UTC in the #openstack-meeting channel.
The agenda for tomorrow's meeting can be found here:
https://wiki.openstack.org/wiki/Meetings/QATeamMeeting
Anyone is welcome to
Hi everyone,
Just a quick reminder that the weekly OpenStack QA team IRC meeting will be
tomorrow Thursday, May 7th at 17:00 UTC in the #openstack-meeting channel.
The agenda for tomorrow's meeting can be found here:
https://wiki.openstack.org/wiki/Meetings/QATeamMeeting
Anyone is welcome to add
On Mon, May 11, 2015 at 02:57:48PM -0700, Joe Gordon wrote:
When learning about how a project works one of the first things I look for
is a brief architecture description along with a diagram. For most
OpenStack projects, all I can find is a bunch of random third party slides
and diagrams.
On Thu, May 14, 2015 at 06:00:01PM +0400, Evgeny Antyshev wrote:
Hello,
We faced the following problem when running tempest on stable/kilo branch:
tempest requires tempest-lib=0.5.0, while global requirements from
stable/kilo ==0.4.0
(module common/ssh was moved from tempest to tempest-lib
On Wed, May 13, 2015 at 02:36:48PM -0700, Joshua Harlow wrote:
Dolph Mathews wrote:
Developers can handle ASCII. Developers can't handle steel blue versus
cornflower blue.
But seriously, graphics collaboratively authored by developers should,
ideally, be editable via a text file. Otherwise
Hi everyone,
Just a quick reminder that the weekly OpenStack QA team IRC meeting will be
tomorrow Thursday, April 16th at 22:00 UTC in the #openstack-meeting channel.
The agenda for tomorrow's meeting can be found here:
https://wiki.openstack.org/wiki/Meetings/QATeamMeeting
Anyone is welcome to
On Mon, Apr 06, 2015 at 02:25:14PM -0400, David Kranz wrote:
There have been a number of changes in tempest recently that seem to
coordinate with devstack that are a bit unclear.
Well, the issue was that before tempest was making all sorts of incorrect
implicit assumptions about the underlying
On Mon, Apr 06, 2015 at 01:17:20PM -0500, Matt Riedemann wrote:
On 4/6/2015 9:46 AM, Chris Friesen wrote:
On 04/06/2015 07:56 AM, Ed Leafe wrote:
On Apr 6, 2015, at 1:21 AM, Chris Friesen chris.frie...@windriver.com
wrote:
Please feel free to add a blueprint in Launchpad. I don't see
On Wed, Apr 08, 2015 at 01:08:03PM -0400, David Kranz wrote:
Since tempest no longer uses the official clients as a literal code
dependency, except for the cli tests which are being removed, the clients
have been dropping from requirements.txt. But when debugging issues
uncovered by tempest,
On Thu, Apr 09, 2015 at 04:00:39PM -0500, Matt Riedemann wrote:
On 4/9/2015 3:14 PM, Kyle Mestery wrote:
The Neutron team is proud to announce the release of the latest version
of python-neutronclient. This release includes the following bug fixes
and improvements:
aa1215a Merge Fix one
On Wed, Jun 03, 2015 at 09:06:29AM -0500, Matt Riedemann wrote:
Following on the thread about no longer doing stable point releases [1] at
the summit we talked about doing icehouse-eol pretty soon [2].
I scrubbed the open stable/icehouse patches last week and we're down to at
least one
On Mon, Jun 22, 2015 at 11:41:56AM -0400, David Kranz wrote:
On 06/22/2015 10:15 AM, Yaroslav Lobankov wrote:
Hello everyone,
I have some questions about the bug triage procedure for Tempest:
1. Some bugs in Tempest have status Fix committed. Should we move
statuses of these bugs to Fix
Hi Everyone,
I'd like to propose we add Jordan Pittier (jordanP) to the tempest core team.
Jordan has been a steady contributor and reviewer on tempest over the past few
cycles and he's been actively engaged in the Tempest community. Jordan has had
one of the higher review counts on Tempest for
Hi everyone,
Just a quick reminder that the weekly OpenStack QA team IRC meeting will be
tomorrow Thursday, June 25th at 22:00 UTC in the #openstack-meeting channel.
The agenda for tomorrow's meeting can be found here:
https://wiki.openstack.org/wiki/Meetings/QATeamMeeting
Anyone is welcome to
On Thu, Jun 18, 2015 at 02:13:56PM -0400, David Kranz wrote:
We had a discussion about this at the qa meeting today around the following
proposal:
tl;dr The test accounts feature provides the same functionality as the
embedded credentials. We should deprecate the account information embedded
So I need to point out that the openstack-qa list isn't used anymore. We only
keep it around so we have a place to send for periodic test results. In the
future you should just send things to the openstack-dev ML with a [QA] tag
in the subject.
On Tue, Jun 16, 2015 at 05:25:30AM +, Tikkanen,
On Mon, Jun 22, 2015 at 04:23:30PM -0400, Matthew Treinish wrote:
Hi Everyone,
I'd like to propose we add Jordan Pittier (jordanP) to the tempest core team.
Jordan has been a steady contributor and reviewer on tempest over the past few
cycles and he's been actively engaged in the Tempest
On Thu, Jul 02, 2015 at 09:22:03PM +0100, Dave Walker wrote:
On 29 June 2015 at 04:59, Robert Collins robe...@robertcollins.net wrote:
Hi, so we're nearly ready to deprecate the python-version-specific
requirements files. Once we have infra's requirements cross checking
jobs all copacetic
On Wed, Jul 01, 2015 at 03:30:55PM -0500, Douglas Mendiz?bal wrote:
Hi Asha,
The blueprint you linked for Tempest is over a year old. I think it
pre-dates the Tempest team's decision to stop putting all project
tests in the same repo. I believe the spec is obsolete, but someone
from the
101 - 200 of 368 matches
Mail list logo
