Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Robert Klemme <shortcutter@googlemail.com>
Newsgroups: comp.lang.ruby
Subject: Re: debugger changes test behavior
Date: Wed, 05 Mar 2014 20:46:50 +0100
Lines: 18
Message-ID: <bnpd9bFru5sU1@mid.individual.net>
References: <732a6b69-7708-4f43-a95f-d766d42e6a3f@googlegroups.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: individual.net mKWiiyVDRJHS3E3oN1tbFQkjRpaDTIcuCHWgixf1MSn/u5+BQ=
Cancel-Lock: sha1:2/9wgBBueauxJSWyzEknLk54KuU=
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
In-Reply-To: <732a6b69-7708-4f43-a95f-d766d42e6a3f@googlegroups.com>
Xref: csiph.com comp.lang.ruby:6925

On 05.03.2014 17:16, Michel Pigassou wrote:

> Have you ever had this problem where your test fails where it should
> succeed, and you just add a debugger in your controller or model, and
> then it succeeds?
>
> I could observe this behavior under different Ruby versions, 1.9.3
> and 2.0.0, with Rails 3 and 4. I have no idea what could cause this,
> but since I have been noticing this many times I guess I'm not the
> only one. Am I?

That could be anything, for example timing in multithreaded applications 
or the debugger changing meta programming effects.

Cheers

	robert