search for: brittle

...e: > > On Mon, Dec 3, 2018 at 11:49 PM John McCall jmccall at apple.com wrote: > > Piotr's proposal unfortunately doesn't give us a good name for the class > of optimizations that require being listed in supported_optimizations. > In earlier discussions I called them "brittle", but I can understand why > nobody wants to call their optimization that, so let's call them > "good-faith optimizations" instead since they rely on the good faith of > all the participating code. > > Every optimization has to know how to maintain the structural r...

...riends_with(befriended) friend = self.new friend.befriender = befriender friend.befriended = befriended befriender.group.friends << friend friend else return end end Should I be breaking this up into smaller methods? Is there a better way to do it? Is my design brittle or convoluted? How would I write a Unit Test for the above? Really stupid questions: why do I need the "friend" right before the else? I know these are a lot of questions but I really can''t find any good information out there about good design patterns for an integrated rails...

...t, the controller deliberately stops 20% of users logging in - flash contains "You''re not getting in because I say so" In both these cases the only thing that varies from the user side (and therefore the functional test) is the flash. However, this seems to be extremely brittle to me: if I were to change the message then the tests fail. Is there a preferred way to cope with this other than refactoring my tests not to use the flash? The best solution I can come up with is to keep all interface text in a external gettext file and compare the flash and the expected v...

Hello, I have several asterisk 1.2.7.1 servers connected through iax2 and often the local asterisk would no longer see the remote one, even thought the link is high quality and the ping is perfect. Is there some issues to take into account about IAX2 connections? Is asterisk's DNS resolution too fragile and should I use raw IP's in my configs? Thanks for any help (I'm in hot

Hi there, Whilst trying to come up with a minimal configuration for Dovecot: http://dabase.com/blog/Minimal_Dovecot/ I noticed the configuration syntax is a bit admin unfriendly. It's easy to get an infamous Error code 89. Is there any back story to the grammar or language this configuration is in? Kind regards,

...ted object, so that I can make some assertions on it. But I can''t seem to find an elegant way of doing that. Of course, might create action redirects. That means that @response.redirect_url is something like "/show/8". So I could pluck the number off that, but that seems too brittle, since if I change my routing, that would no longer work. I was wondering if there was a way to call routing on the redirect_url, so that I could then fetch the ID from the parameters hash. That wouldn''t be brittle at all. But I can''t seem to find any documentation for routing...

...wiki.rubyonrails.com/rails/pages/HowtoMakeAbstractModel> http://wiki.rubyonrails.com/rails/pages/HowtoMakeAbstractModel. Which looks pretty hackish to me. Is there any best way or recommendations on how to achieve this kind of behavior? I know I could modify ActiveRecord directly, but that seems brittle -- to run my app on later versions of rails, I''d have to remember to re-modify ActiveRecord. What''s really brittle, though, is my brain. This is my first RoR app, and parts of rails (convention over config, built-in ORM and testing) I immediately loved. But some stuff seems like...

I''m planning on setting up an NFS server for our ESXi hosts and plan on using a virtualized Solaris or Nexenta host to serve ZFS over NFS. The storage I have available is provided by Equallogic boxes over 10Gbe iSCSI. I am trying to figure out the best way to provide both performance and resiliency given the Equallogic provides the redundancy. Since I am hoping to provide a 2TB

...s. Then we start using mocks at object level to use them as a design tool, and so we implement the different layers of the system. After implementing the inner layer, the story should pass. When that happens we could remove the mocks and replace it with calls to the real code, making the suite less brittle (except for calls to external services/databases/file systems). So if the story passes all acceptance tests, why is there a need for examples at a lower level? -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/rspec-users/attachments/200...

On Mon, Dec 3, 2018 at 11:49 PM John McCall <jmccall at apple.com> wrote: > Piotr's proposal unfortunately doesn't give us a good name for the class > of optimizations that require being listed in supported_optimizations. > In earlier discussions I called them "brittle", but I can understand why > nobody wants to call their optimization that, so let's call them > "good-faith optimizations" instead since they rely on the good faith of > all the participating code. > > Every optimization has to know how to maintain the structural r...

...owed the instructions to the dot. Everything builds fine. But, when 'make load' the whole machine will freeze. Anyone had the same problem and managed to solve it? I'm using a Billion HFC PCI card on Trustix 2.0 running kernel 2.4.26. As a side note, I feel that the bri-stuff is too brittle. For starters, it doesn't work with * 1.0RC2 and I've a feeling it won't work with 1.0 final as well. Perhaps the community has to coerce kapejod to get bri-stuff work with mainstream * versions? Just my $0.02. Cheers and TIA. Leo

...spec). This keeps the noise of what is necessary but uninteresting (from the perspective of the tests) out of the way of the test methods, which can focus entirely on the interesting bits. The motivation is the same as Nat Pryce''s - expecting only the interesting bits will make tests less brittle - but the resulting principle revolves on a different axis. Thoughts on this? Cheers, David

I''m curious, Christian Neukirchen has released test/unit[1] that seems to mirror much of RSpec, but built on Test::Unit, so in some ways less brittle from a Rails-integration perspective, and also allowing you to mix the two together as appropriate. So, has anyone made an informed comparison? I''m new enough that I don''t really know the finer points yet. The syntax is slightly different, but that seems like a minor issue Chris...

Hey, Sorry for so many questions - I''m really bad at this right now. I''m trying to cover the following code w/ rspec def index if params[:user_id] @user = User.find(params[:user_id]) @messages = @user.messages end end So basically what I''m doing is listing all the messages for a user, provided there is an id parameter. describe

...X86/2012-01-12-extract-sv.ll:12 > +; CHECK-NEXT: vblendps {{.*#+}} xmm1 = xmm1[0],xmm2[1,2,3] > +; CHECK-NEXT: vpermilps {{.*#+}} xmm0 = xmm0[0,0,0,0] > ; CHECK-NEXT: vinsertf128 $1, %xmm0, %ymm0, %ymm0 > ---------------- > greened wrote: >> Can we make this test less brittle by using FileCheck variables? >> This goes for pretty much every test in this patch. > I'm sorry but no - its been repeatedly proven that using > update_llc_test_checks.py on the majority of x86 tests is the way > forward - it speeds up creation of tests (x86 by far has the highe...

...t; code would not change many tests at all. If someone is worried about prolog/epilog code then there should be tests specifically targeted to that. Not every test needs to include CHECK lines for that stuff. I am not suggesting tests need to be perfect, just that we should try to make them less brittle as we go along, incrementally. >> If a test is looking for different behavior based on register use, then >> of course the test should be written to detect specific register uses. >> If the register use changes, the test fails because a bug was >> introduced. >> >&...

...phe wrote: > >>Find attached two patches I have in order to build klibc 2.0.2 > >>against kernel 3.8.13 > >>We had to introduce those patches when going from kernel 3.6 to kernel 3.7 > >>Hope it helps. > >> > >those patches are wrong and again very brittle. > > > >just use the way it is described in `make help': > > > >A) cd ~/src/linux > > make defconfig > > make headers_install > > > >B) cd ~/src/klibc > > make KLIBCKERNELSRC=`pwd`/../linux/usr/ > > > > > Sorry, but...

...18-December/msg00064.html Using the info mention there I was able to part hand / part sw re-write an XML where I would remove PCI bus references above the value of 8 and re-address the per interface PCI info to use the function field (I don’t need hot pluggable). But the process I’ve built is brittle. Wondering what options i might have to better deal with this PCI issue. Is there a way to tell virt-install, when building the info it passes to qemu, to use the function field during the PCI assignment process so as to support many more interfaces before hitting the PCI bus == 8 issue? If...

Here is my unit test code. post :login, :user=>{ :login => "bob", :password => "test"} assert_response :redirect assert_session_has :user assert_redirected_to :action => ''welcome'' Here is the failure I''m getting when I run my tests. 2) Failure: test_login_required(UserControllerTest)

...2) It makes updating PHI nodes using sets of predecessors incredibly hard 3) There is no correspondence between the edges and the PHI node entries other than number, making most of the code that does handle this very ad-hoc "count off N repetitions of the same thing" style code, which is brittle and hard to test effectively. 4) I suspect bugs are quite common given that PHINode::removeIncomingValue accepts a basic block but only removes the first incoming value, leaving the others in place. I can't see any serious use case for this symmetry either. These aren't uses (and can't...