<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Frank Shearar wrote:
<blockquote
cite="mid:CAJbhyRFgMm0-c-d-fLYPVh0pn3Si5a-qpE4X78QYiyruudCrSQ@mail.gmail.com"
type="cite">
<pre wrap="">This guy, and associated/similar tests, has/have become unstable.
Prior to build #339 they just worked. From #340 onwards they sometimes
pass, sometimes fail.
According to the manifests we publish as part of each build the change
from 339 to 340 is just
< Files (cmm.119)
---
</pre>
<blockquote type="cite">
<pre wrap="">Files (cmm.120)
</pre>
</blockquote>
<pre wrap=""><!---->
which seems completely unrelated!
If it weren't for the fact that everything in the test happened in the
context of the main World thread (whatever its proper name is), I'd
think it was a race: the tests consist of
* perform a UI action
* check that the UI's showing what we expect - that there's a list
morph somewhere in the UI whose contents match some list.
I've tried debugging these, and they're annoyingly non-deterministic.
I've often found that rerunning the test - run it til it fails, rerun
the failing assertion - makes the test pass!
Any thoughts?
frank
</pre>
</blockquote>
A very general observation, I have had issues in the past with
non-deterministic tests that turned out to be related to Sets returning
items in a random way.<br>
Scroll down to "<i>The cause of this is a change in behaviour of
Collection>>#difference:"<br>
</i>at <a class="moz-txt-link-freetext" href="http://www.iam.unibe.ch/pipermail/moose-dev/2012-May/012113.html">http://www.iam.unibe.ch/pipermail/moose-dev/2012-May/012113.html</a><br>
<br>
-ben<br>
<br>
</body>
</html>