Jay Pipes writes:
> Someone mentioned automated testing of upgrade paths. This is exactly
> what needs to happen. Hopefully the Tempest folks can work with the CI
> team in the G timeframe to incorporate upgrade path testing for the
> OpenStack components.
I am strongly in favor of this. :)
-J
Maru Newby writes:
> Hi Salvatore,
>
> I see you're working on getting plugins testable with tox:
>
> https://review.openstack.org/#/c/11922/
>
> What about keeping the plugins isolated for testing purposes? I have
> been unable to work on it yet, but I was thinking it might be a good
> idea to
Hi,
I've updated the meetbot that lives in #openstack-meeting to require a
"meeting name" argument after "#startmeeting". This meeting name will
be used in the path to the meeting logs. In the future, if you are
going to start (for example) the Nova team meeting, you should say:
#startmeeting
Scott Lavender writes:
> Does anyone know how to suppress the build started messages from Jenkins?
> We have three gate jobs that are triggered by uploads to Gerrit. The
> Gerrit change-set receives a single start message for each Jenkins job, and
> a single message reporting the results of all t
Hi,
As mentioned in the thread "Jenkins and transient failures", we've had
an unusually high number of transient failures in Jenkins lately. We've
done several things in response to that:
1) Monty identified a problem with our pypi mirror which was the cause
of many of the errors, and corrected
Dan Prince writes:
> If someone wants to split openstack-common changes into patchsets that
> might be Okay in small numbers. If you are merging say 5-10 changes
> from openstack common into all the various openstack projects that
> could translate into a rather large number of reviews (25+) for
Andrew Bogott writes:
> I. As soon as a patch drops into common, the patch author should
> submit merge-from-common patches to all affected projects.
> A. (This should really be done by a bot, but that's not going to
> happen overnight)
Actually, I think with our current level of tooli
"Kevin L. Mitchell" writes:
> One of the things that's really bugging me these days is transient
> failures, such as the inability to download a package, causing a gate
> job to fail. It seems to me that we can distinguish "test failure" from
> "environment build failure" easily enough, and auto
Julien Danjou writes:
> Looking for the check manually here:
>
>https://jenkins.stackforge.org/view/Ceilometer/job/gate-ceilometer-merge/
>
> seems to show that build #73 was related to this request but it has been
> successful. But it reviews and reports as "LOST".
Jenkins was missing the n
Eoghan Glynn writes:
> So I'm wondering whether the CI side-of-the-house would be prepared to
> enable this temporarily on the Jenkins slaves, by running:
>
>echo 0 | sudo tee /proc/sys/kernel/yama/ptrace_scope
>
> prior to the glance tests being kicked off, then reverting straight after.
Je
Hi,
It looks like there are intermittent, but frequent, failures in the
devstack-gate. This suggests a non-deterministic bug has crept into
some piece of OpenStack software.
In this kind of situation, certainly could keep re-approving changes in
the hope that they will pass the test and merge, b
John Postlethwait writes:
> Hello Everyone!
>
> I have a review up that keeps failing the integration tests on Jenkins
> due to some sort of dependency issue. I am not really sure what the
> issue is, but the stack trace in the console output is complaining
> about "No module named version tools
Johannes Erdfelt writes:
> On Tue, Jun 05, 2012, James E. Blair wrote:
>> One important difference is that the new system does not have
>> "retrigger" buttons in Jenkins. If the gate tests fail with a false
>> negative, you'll need to leave another "Ap
Johannes Erdfelt writes:
> There appears to have been some changes to Jenkins recently. Jobs do not
> appear to be associated with Gerrit changes anymore.
>
> https://jenkins.openstack.org/job/gate-nova-python27/
>
> You can see jobs 335 and older have a link to Gerrit, but new jobs don't
> have
Hi,
We have just changed the way Jenkins jobs are triggered for Gerrit
changes. This is another in a series of changes we're rolling out
based on needs described at the design summit.
We had been using the Gerrit Trigger Plugin to launch check and gate
jobs, but we're starting to run up against
On 06/04/2012 05:47 PM, Gabe Westmaas wrote:
Should we revert this change till we get it cleared up?
Here's a proposal to do that:
https://review.openstack.org/#/c/8166/
-Jim
___
Mailing list: https://launchpad.net/~openstack
Post to : openst
On 06/04/2012 04:00 PM, Kevin L. Mitchell wrote:
Today I've noticed some significant problems with nova's test suite
leaving literally hundreds of python processes out. I'm guessing that
this has to do with the unit tests for the multiprocess patch, which was
just approved. This could be causin
Duncan McGreggor writes:
>> And for "announce": who gets the right to post to it ? Or
>> rather, who gets to moderate the posts to it ? PPB ? PTL/relmgr ? Any
>> volunteer ?
Release announcements, and security updates should go to the announce
list, so it seems reasonable to allow the release an
On 05/11/2012 02:04 PM, Mark McLoughlin wrote:
On Fri, 2012-05-11 at 13:57 -0700, David Lutterkort wrote:
On Fri, 2012-05-11 at 12:37 +0100, Mark McLoughlin wrote:
- Our history is far from "clean history", it's pretty disgusting
really. The ratio of interesting commits to merge commits
Mark McLoughlin writes:
> Hey,
>
> So, one thing came really stuck out to me when comparing our process to
> the kernel process:
>
> In the kernel process, maintainers are responsible for running
> 'git-merge' and they see it as their job to resolve conflicts.
>
> In our process, Jenkins r
Mark McLoughlin writes:
> Hey,
>
> We discussed this during the "baking area for features" design summit
> session. I found that discussion fairly frustrating because there were
> so many of us involved and we all were either wanting to discuss
> slightly different things or had a slightly differ
Chris Behrens writes:
> I'm noticing that core reviewers aren't tagged as a +2 anymore in the
> general review box. Instead, it just shows a check. (Except for my
> own reviews, which show as a +2). I have to look at the review
> comments to see if others voted +2 now.
A check mark is equival
Hi,
We've just upgraded Gerrit to version 2.3. There are a lot of changes
behind the scenes that we've been looking forward to (like being able to
store data in innodb rather than myisam tables for extra data
longevity). And there are a few visible changes that may be of interest
to OpenStack de
On 04/05/2012 07:12 PM, Jason Kölker wrote:
On Fri, 2012-04-06 at 00:04 +, Brian Lamar wrote:
Can anyone enlighten me as to why the gate-melange-unittests-python26 job is
only running a single test? The first time it ran it correctly found all 500+
tests but now it seems to be just running
Justin Santa Barbara writes:
> This is a plugin for OpenStack; it won't support any other clouds. This
> means there will be no baggage from having to support EC2, or any of the
> other clouds that JClouds supports. We can support all the OpenStack
> goodness directly.
I second Andrew's commen
Jim Meyering writes:
> Future cloners (and those who push, too) will be
> grateful if someone with access to the server would
> do the same thing to the public nova.git repository.
> Compressing the repo improves server performance, too.
Hi,
That's a good idea, thanks for the suggestion! I wan
Indeed, as soon as someone says "I have Tempest working on a system
configured by devstack with a repeatable process, here's how I did
it..." we'll start running it in Jenkins. But so far I've heard from
the Tempest developers that it's not quite ready yet.
-Jim
David Kranz writes:
> There is
Jesse Andrews writes:
> There are certainly folks who review changes to stable/diablo
>
> So if you want to propose patches to the branch, please do!
Additionally, the stable/diablo branch of devstack is used in
integration testing to gate commits to the stable/diablo branches of
nova, glance, a
Hi,
The server that was hosting Jenkins was getting a bit long in the tooth,
so this weekend we moved Jenkins to a new one. It is now running on a
cloud server with more CPU and memory so it should be a little more
responsive.
It was built using our puppet module[1], so we have an actual
standar
"Dan Prince" writes:
> Jim,
>
> Okay. I'm still a bit fuzzy on the order of operations we'd need to
> make in order to get branch in when a config file changes.
>
> Take this review for example:
>
> https://review.openstack.org/#change,2919
>
> Based on what I understand devstack needs t
cor...@inaugust.com (James E. Blair) writes:
> In short, the process for new developers will be:
>
> 1) Sign CLA via Echosign
> 2) Record signature in wiki
> 3) Apply for membership in openstack-cla
> 4) Contribute!
This change is in place; membership in openstack-cla is re
Hi,
We encountered some problems today that delayed several patches from
going in (I believe they have all been merged now). It was a bit of a
rough day, but I'm pleased that several people pitched in to help
identify and solve those problems, and we've made some good progress
overall. Here's a
Mark McLoughlin writes:
> Nice work. Do you have a sense of how many past contributors haven't
> signed the CLA or added themselves to the wiki?
I don't know.
> Also, how does this work for the corporate CLA?
We're not changing the CLA process at all, so the existing process still
stands:
"Dan Prince" writes:
> Hi Jim,
>
> A couple of questions for you:
>
> 1) You mentioned how to coordinate changes between glance and nova but
> what about devstack. Does that same process apply to devstack as well?
> For example if there were a configuration file change (api-paste
> changes of
Hi,
We've gotten some requests from core reviewers to automate verification
that people submitting changes have agreed to the CLA. Right now, the
expectation is that core reviewers will only approve changes submitted
by people who have agreed. That's silly because we have computers that
can do t
Hi,
A few weeks ago, I wrote about turning on an integration test gating job
for the stable/diablo branch. That's been running for a while now, and
during that time with help from Anthony Young and Jesse Andrews, we've
been able to address the issues we saw and make the job fairly reliable.
At t
cor...@inaugust.com (James E. Blair) writes:
> Hi,
>
> Monty and I have been working on a solution to a number of problems
> and suggested enhancements to Gerrit. In short, we're planning on
> adding a new review type to Gerrit so that a core reviewer can
> specif
Hi,
Monty and I have been working on a solution to a number of problems
and suggested enhancements to Gerrit. In short, we're planning on
adding a new review type to Gerrit so that a core reviewer can
specifically mark a review as "Approved" for Jenkins to test and
merge. This will end our overl
Ziad Sawalha writes:
> Very cool!
>
> Any plans to have a silent (or daily, or on demand) one running against
> trunk for all projects?
Yes, our next focus will be on a post-commit integration test job for
trunk. That means we don't have to have all the technical problems
solved before we start
Hi,
A lot of people would like to see us with more commit gating jobs that
test functionality across the full range of core OpenStack projects.
We've made some progress in that direction, and I think we can start
some limited testing by turning on a gating job for the stable/diablo
branch of sever
Mark McLoughlin writes:
> On Fri, 2011-11-11 at 12:11 +0400, Yuriy Taraday wrote:
>> I wonder if we should keep Change ID consistent in stable and master
>> branches so that if one merged something into master, reviewers
>> and archaeologists can easily find both related changes in master and all
Mark McLoughlin writes:
>> To mitigate that, we decided that the group doing stable branch
>> maintenance would be a separate group (i.e. *not* core developers), and
>> we decided that whatever ends up in the stable branch must first land in
>> the master branch.
>
> Well, I recall it a little di
Nati Ueno writes:
> Hi folks
>
> stable/diablo nova didn't pass pep8 now.
> https://bugs.launchpad.net/nova/+bug/885540
>
> - Can we have pep8 check automatically for diablo/stable?
> - How about unit-testing on merge props for diablo/stable?
> - Can we have Jenkins task for diablo/stable ?
Hi,
Vishvananda Ishaya writes:
> Speaking of keystone diablo tag, it is currently missing the following commit:
>
> https://github.com/openstack/keystone/commit/2bb474331d73e7c6d2a507cb097c50cfe65ad6b6
>
> This commit is required for the ec2 api to work with keystone. Seems like we
> need to move t
Mark McLoughlin writes:
> Cool stuff. I don't care much about the name, but I'd call it
> diablo-stable
I've set up a branch called "stable/diablo". The launchpad team
openstack-stable-maint will be able to +2 all "stable/*" branches.
>> > Does the current diablo branch for Nova pass all tests
Mark McLoughlin writes:
> Chuck pointed out on IRC that I forgot to mention the other projects.
>
> I totally think we should do the same for all projects, I was just using
> Nova as a testcase.
Yep.
>> > Each project will have a branch named after the previous release. For
>> > example, the st
Julien Danjou writes:
> This sounds like a good idea, but the name is very generic and the code
> only related to OpenStack. I am not sure it's a good idea to keep that
> name or to write the tool as it is now.
>
> There's a need to have something automated to push things to gerrit. I
> think you
Chris Wright writes:
> * Mark McLoughlin (mar...@redhat.com) wrote:
>> On Wed, 2011-10-12 at 13:58 -0400, James E. Blair wrote:
>> > Mark McLoughlin writes:
>> > > Anyone can propose a cherry-pick to the maintainers. This helps ensure
>> > > that the
Gabe Westmaas writes:
> First, there was widespread agreement that in order for an integration
> suite to be run in the openstack jenkins, it should be included in the
> community github repository.
Hi,
During the meeting today, folks asked about what the core group is for
the openstack-integra
Mark McLoughlin writes:
> Hey,
>
> I've posted a proposal for how the stable branch could work here:
>
> http://wiki.openstack.org/StableBranch
>
> and a proposed diablo branch for nova:
>
> http://github.com/markmc/nova/tree/diablo
>
> The wiki page seems to be 404 for folks for some bizarre
Mark Gius writes:
> When you say "combined into one update," do you mean that changes are pushed
> every 15 seconds, or that multiple commits in Gerrit get combined before
> pushing to github?
Changes are pushed as-is within 15 seconds. The repo is an exact
mirror, no commit rewriting or any ot
Mark McLoughlin writes:
> On Mon, 2011-09-26 at 09:33 +0200, Thierry Carrez wrote:
>> Jesse Andrews wrote:
>> > Is there / will there be a git tag/branch for diablo in the
>> > github.com/openstack/nova repository?
>>
>> That's a good question... Release tags were only appearing in the
>> miles
Lorin Hochstein writes:
> What's the location of the gerrit git repository? Is it this:
> https://review.openstack.org/p/openstack/nova
The official repository for nova is at https://github.com/openstack/nova
which puts the GIT urls at either:
git://github.com/openstack/nova.git
or
https:
Hi,
Quantum moved its code hosting to GitHub this morning, and is now using
Gerrit for code reviews. We're currently gating the trunk on the test
suite and pep8. Pylint is currently a post-merge job, but making it a
pre-merge check is a future to-do once the count comes down.
As part of the inc
Johannes Erdfelt writes:
> On Wed, Sep 07, 2011, Sandy Walsh wrote:
>> ... and that's only from my first few days using Gerrit.
>
> I'd also like to add that the when merges fail, it's not easy to figure
> out why.
>
> I had a proposed branch the was approved and then failed to merge. I
> recei
Johannes Erdfelt writes:
> I reviewed the updated documentation and made all of the changes to my
> local config. However, when I run 'git review', I get this error:
>
> johannes@compute1:~/openstack/glance/johannes$ git review
> Successfully rebased and updated refs/heads/protection.
> fatal: '/
Hi,
Monty and I have added a script originally from the Gluster project to
the Glance and Keystone repositories. It's designed to make the initial
setup of a newly cloned Git repository with Gerrit easier, and to smooth
the process of submitting changes. We expect to use the same process
with Sw
Yuriy Taraday writes:
> Hello.
>
> So, I'm still trying to understand how to work with Gerrit.
> I've uploaded series of commits to Gerrit. One of them is
> https://review.openstack.org/159. Patchset has been changed several times
> then merged then reverted, but change is still in Merged status.
Yuriy Taraday writes:
> I have series of commits that can be applied separately and can be treated
> as separate improvements in my branch.
> That commits were there before I knew that I should install Gerrit hook.
> Now I have bunch of commits without Change-Id while commit --amend works
> only
cor...@inaugust.com (James E. Blair) writes:
> I'll work on updating our import script to fix the rest of the
> accounts and send out another email to this list when that is
> complete.
Monty has fixed the Launchpad sync script so that publicly available
emails should correctly sho
Yuriy Taraday writes:
> Thanks to he fix, "invalid author" problem vanished.
> Now I'm getting "missing Change-Id in commit message" error.
> What is the best way to provide Change-Id to existing commits?
>
> Kind regards, Yuriy.
We've seen two ways of getting commits without Change-Ids from
rep
Yuriy Taraday writes:
> Hello.
>
> I'm trying to use Gerrit to propose changes to Keystone.
> I'm using instructions from http://wiki.openstack.org/GerritWorkflow to push
> my changes.
> I'm getting "invalid author" error but my settings/contacts page looks fine
> and the e-mail listed there and
62 matches
Mail list logo
