Morgan,
Good catch. This can be easily fixed if we add special tag in commit
message: e.g. #no-coverage-check
Best regards,
Boris Pavlovic
On Sun, Apr 19, 2015 at 9:33 AM, Morgan Fainberg
wrote:
> This is an interesting idea, but just a note on implementation:
>
> It is absolutely
Gordon,
+1. i don't think this would be a good idea as a non-voting job either as
> it can/will lead to lazy reviews.
It is similar to say let's remove unit/functional/pep8/pylint/"any other
testing" because it will lead to lazy reviews.
Best regards,
Boris Pavlovic
her reviewers ensures that tests are well written.
P.S. Unit tests are the first criteria of code quality: if it is hard to
cover code by unit tests, code is bad written
and should be refactored.
Best regards,
Boris Pavlovic
On Mon, Apr 20, 2015 at 5:26 PM, Dan Smith wrote:
> > Well, I think t
Jeremy,
Thank you for explanation, I missed this point before.
Best regards,
Boris Pavlovic
On Mon, Apr 20, 2015 at 6:06 PM, Jay Pipes wrote:
> +1, Jeremy. Excellent points.
>
> -jay
>
>
> On 04/20/2015 10:59 AM, Jeremy Stanley wrote:
>
>>
>>
>> On 2
e useful as an automated
> pointer to how things probably should be, but sometimes it's entirely
> o-k to regress this number a few points.
Diffs between reports is almost ready.
Best regards,
Boris Pavlovic
On Mon, Apr 20, 2015 at 7:59 PM, Clint Byrum wrote:
> Excerpts from Boris Pavl
unit tests, we should keep our test coverage :(
Best regards,
Boris Pavlovic
On Mon, Apr 20, 2015 at 9:11 PM, Hayes, Graham wrote:
> On 20/04/15 18:01, Clint Byrum wrote:
> > Excerpts from Boris Pavlovic's message of 2015-04-18 18:30:02 -0700:
> >> Hi stackers,
> >&
y* interested to know that I got 100% decision (or even
> boolean) coverage on the specific lines of the feature I just added by
> running just the unit tests that exercise it.
And this is exactly what "tox -e cover" does and job that run tox -e cover
in gates.
Best regards,
B
"tox" runs cover job by default, most developers will make it pass
before sending patch on review.
Best regards,
Boris Pavlovic
On Wed, Apr 22, 2015 at 5:00 PM, David Stanek wrote:
>
> On Sat, Apr 18, 2015 at 9:30 PM, Boris Pavlovic wrote:
>
>> Code coverage is one of
+1! finally!=)
Best regards,
Boris Pavlovic
On Tue, May 5, 2015 at 5:57 PM, Davanum Srinivas wrote:
> +1 from me!!
>
> -- dims
>
> On Tue, May 5, 2015 at 10:47 AM, Julien Danjou wrote:
> > Hi fellows,
> >
> > I'd like to propose that we add Joshua
Roman,
Well done! This really simplifies life!
Best regards,
Boris Pavlovic
On Tue, May 5, 2015 at 4:07 PM, Mikhail Dubov wrote:
> Hi Roman,
>
> a truly great job. Very impressive and useful. Thanks a lot!
>
> Best regards,
> Mikhail Dubov
>
> Engineering OPS
> M
+Rally team
Just to make sure that everybody saw this.
Best regards,
Boris Pavlovic
On Tue, May 5, 2015 at 6:19 PM, Mikhail Dubov wrote:
> Hi everyone,
>
> sorry for the previous disinformative message. We have decided to move our
> weekly meeting to Wednesdays at 14:00 UTC (IRC,
Mike,
Thank you for picking up dates. I am OK with them.
Best regards,
Boris Pavlovic
On Tue, May 5, 2015 at 6:22 PM, Mikhail Dubov wrote:
> Hi Rally team,
>
> as mentioned in another message from me in this list, we have decided to
> use the meeting time on Wednesdays at 14:00
. =(
Best regards,
Boris Pavlovic
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo
+1!
On Thu, May 7, 2015 at 7:24 PM, Mike Bayer wrote:
>
>
> On 5/7/15 11:01 AM, Joshua Harlow wrote:
>
>> +1 for Mehdi, hooray to that!
>>
>> http://gph.is/19n19VQ (haha),
>>
>> -Josh
>>
>
>
> +1, welcome aboard
>
>
>
>
>> ozamiatin wrote:
>>
>>> +1 for adding Mehdi to oslo-core!
>>>
>>> Thanks,
Sean,
Nobody is able to track and know *everything*.
Friendly reminder that Heat is going to be removed and not installed by
default would help to avoid such situations.
Best regards,
Boris Pavlovic
On Thu, May 7, 2015 at 8:06 PM, Sean Dague wrote:
> On 05/07/2015 12:51 PM, Boris Pavlo
Sean,
Thank you for advice. We are going to fix jobs ASAP.
Here is the patch: https://review.openstack.org/#/c/181088/
But seems like it's not ready yet.
Best regards,
Boris Pavlovic
On Thu, May 7, 2015 at 8:40 PM, Sean Dague wrote:
> On 05/07/2015 01:37 PM, Boris Pavlovic wrote:
ling saying that there is no heat service=)
Best regards,
Boris Pavlovic
On Thu, May 7, 2015 at 9:29 PM, Joshua Harlow wrote:
> Boris Pavlovic wrote:
>
>> Sean,
>>
>> Nobody is able to track and know *everything*.
>>
>> Friendly reminder that Heat is goin
>
> So... test jobs should be extremely explicit about what they setup and
> what they expect.
+2
Best regards,
Boris Pavlovic
On Thu, May 7, 2015 at 9:44 PM, Sean Dague wrote:
> On 05/07/2015 02:29 PM, Joshua Harlow wrote:
> > Boris Pavlovic wrote:
> >> Sean,
..)?
In Rally this is part of life cycle of running task.
Not sure that it is possible to share it, because it is thigh related to
checking what did you write in task. =)
Best regards,
Boris Pavlovic
On Thu, May 7, 2015 at 9:54 PM, Joshua Harlow wrote:
> Sean Dague wrote:
>
>> O
>
> Couldn't we just use real image files to do this. IIRC, gerrit supports
> displaying image files which are included in a commit. For example, I've
> been
> planning to copy these images:
+1 for real images
Best regards,
Boris Pavlovic
On Tue, May 12, 2015 at
Mike,
Thank you for saying all that you said above.
Best regards,
Boris Pavlovic
On Tue, May 12, 2015 at 2:35 AM, Clint Byrum wrote:
> Excerpts from Mike Bayer's message of 2015-05-11 15:44:30 -0700:
> >
> > On 5/11/15 5:25 PM, Robert Collins wrote:
> > >
> &g
Mike,
Thank you for release notes! Nice work!
Best regards,
Boris Pavlovic
On Thu, May 14, 2015 at 5:48 PM, Mikhail Dubov wrote:
> Hi everyone,
>
> Rally team is happy to announce that we have just cut the new release
> 0.0.4!
>
> *Release stats:*
>
>- Commits: *8
HTML report (which makes it work without
internet)
Best regards,
Boris Pavlovic
On Fri, Mar 24, 2017 at 6:27 AM, Fernando López
wrote:
> Dear all,
>
> I just started to play with Rally and I wonder if I could get the output
> html file with the results of a executed task and o
most
of the functionality.
If you specify what exactly you want to test I can help with writing Rally
Task for that. (it will use as minimum as possible resources)
Best regards,
Boris Pavlovic
On Thu, Apr 6, 2017 at 2:38 AM, Dmitry Tantsur wrote:
> On 04/05/2017 10:49 PM, Emilien Macchi wrot
Hi stackers,
Here are the slides from summit
https://docs.google.com/presentation/d/1QxsQh8E7Tr46KkLPV7QTwBAbTKFtB6dVEv-pQwg6LUA/edit#slide=id.p4
Here is the video
https://www.openstack.org/videos/boston-2017/project-update-rally
Best regards,
Boris Pavlovic
way to align everybody in community and make it
default for all projects.
Best regards,
Boris Pavlovic
On Tue, May 23, 2017 at 2:18 PM, Zane Bitter wrote:
> On 21/05/17 15:38, Monty Taylor wrote:
>
>> One might argue that HA strategies are an operator concern, but in
>> r
#x27;t be able to use plugins that requires admin
role.
This patch finishes works: https://review.openstack.org/#/c/465495/
Thanks to everybody that was involved in this huge effort!
Best regards,
Boris Pavlovic
__
OpenSta
resource information and doing this very very simple and easy placement
selection...
Best regards,
Boris Pavlovic
On Mon, Jun 19, 2017 at 5:05 PM, Edward Leafe wrote:
> On Jun 19, 2017, at 5:27 PM, Jay Pipes wrote:
>
>
> It was from the straw man example. Replacing the $FOO_UUID wi
roperly git review
3) Maybe few tutorials (how to find some bug, how to test it and where are
the docs, devstack, ...)
That would simplify onboarding process...
Best regards,
Boris Pavlovic
On Mon, Jun 26, 2017 at 2:45 AM, Alexandra Settle
wrote:
> I think this is a good idea :) thanks Mike.
/1fa653635781cd975a1031e212b35b6c38196ba4
Best regards,
Boris Pavlovic
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http
Rajul,
It makes sense! However, maybe it's a bit too late... ;)
Best regards,
Boris Pavlovic
On Thu, Aug 3, 2017 at 12:16 PM, Rajul Kumar
wrote:
> Hello everyone
>
> I have added a blueprint on having tail-based sampling as a sampling
> option for continuous tracing in OSProf
Rajul,
May I ask why you think so?
Exposed by OSprofiler issues are going to be really hard to fix in current
OpenStack architecture.
Best regards,
Boris Pavlovic
On Thu, Aug 3, 2017 at 12:56 PM, Rajul Kumar
wrote:
> Hi Boris
>
> Good to hear from you.
> May I ask why you thin
s interface in
such way that it's easy to extend and provide to end user nice user
experience from both side (shell & python) and nice and stable interface
for client developers .
By the way stevedore is really providing very bad plugin experience and
should not be used definitely.
Best r
it won't help community too much to fix the real problems
in architecture (in my opinion it's too late), for example creating VM
performs ~400 DB requests... and yep this is going to be slow, and now
what? how can you fix that?..
Best regards,
Boris Pavlovic
On Fri, Aug 4, 2017 at 1:12 P
/implementation/hook_and_trigger_plugins.html
Best regards,
Boris Pavlovic
On Mon, Aug 14, 2017 at 2:35 AM, Sam P wrote:
> Hi All,
>
> This is a follow up for OpenStack Extreme Testing session[1]
> we did in MEX-ops-meetup.
>
> Quick intro for those who were not there:
> In t
standard and easy way to upgrade
So basically we are not losing anything even if we do not backward
compatible changes and rethink completely architecture and API.
I know this sounds like science fiction, but I believe community will
appreciate steps in this direction...
Best regards,
Boris Pavlo
ogramming language, so
it's sort of big type mismatch and logically wrong. However, what's wrong
with Cobol? If you use right architecture and right algorithms it will
definitely work better than implementation of program in any other language
with wrong architecture and bad algorithms... so n
Jay,
OK, I'll bite.
This doesn't sound like a constructive discussion. Bye Bye.
Best regards,
Boris Pavlovic
On Thu, Sep 14, 2017 at 8:50 AM, Jay Pipes wrote:
> OK, I'll bite.
>
> On 09/13/2017 08:56 PM, Boris Pavlovic wrote:
>
>> Jay,
>>
>> All
Chandan,
Not a big expert in Kola, but I have the same task for
containerizing Rally.
The solution is simple, just use ENTRYPOINT like here:
https://github.com/openstack/rally/blob/master/Dockerfile#L38 (but for
tempest)
Best regards,
Boris Pavlovic
On Mon, Oct 9, 2017 at 10:08 PM, Chandan
Hi,
Someone somehow deleted 0.9.* branches from GitHub repo
https://github.com/openstack/rally
A lot of end users are using these branches and are affected by this
change.
Can someone help to restore them?
Best regards,
Boris Pavlovic
ads in
parallel (and generate more realistic load)
-.
So it would be really nice if you can share gaps that you faced that are
blocking you to use directly Rally..
Thanks!
Best regards,
Boris Pavlovic
On Tue, Oct 31, 2017 at 10:50 PM, Sam P wrote:
> Hi All,
>
> Sending out a gen
github.com/openstack/rally/blob/master/doc/specs/in-progress/hook_section.rst
You are very welcome to join this effort and help Rally team deliver it
faster.
Thanks!
Best regards,
Boris Pavlovic
On Wed, Aug 31, 2016 at 11:55 PM, Jorge Cardoso (Cloud Operations and
Analytics, IT R&D Divisio
Andrey,
Great news!
Best regards,
Boris Pavlovic
On Wed, Apr 11, 2018 at 9:14 AM, Andrey Kurilin
wrote:
> Hi Stackers!
>
> Today I am happy to announce great news!
>
> From a historical perspective, Rally is testing (benchmarking) tool for
> OpenStack, but it is changed. M
plemented as a single Rally task which is quite convenient.
Best regards,
Boris Pavlovic
On Wed, Nov 30, 2016 at 6:02 AM, Dulko, Michal
wrote:
> On Mon, 2016-11-28 at 15:51 +0300, Timur Nurlygayanov wrote:
> > Hi OpenStack developers and operators,
> >
> > we are going to cr
Jean-Philippe,
> s/COBOL/go/g and it makes your comment even funnier.
It makes it scary =)
Best regards,
Boris Pavlovic
On Tue, Dec 13, 2016 at 2:24 AM, Jean-Philippe Evrard <
jean-philippe.evr...@rackspace.co.uk> wrote:
> s/COBOL/go/g and it makes your comment even funni
301 - 345 of 345 matches
Mail list logo
