On 29 November 2012 13:11, Peter Firmstone wrote:
> The last passing trunk versions:
>
> Jdk6 Ubuntu 1407017
> Solaris x861373770
> Jdk7 Ubuntu 1379873
> Windows 1373770
>
> Revision 1373770 looks the most stable, I think all platforms were passing
> on this, 1407017 o
The last passing trunk versions:
Jdk6 Ubuntu 1407017
Solaris x861373770
Jdk7 Ubuntu 1379873
Windows 1373770
Revision 1373770 looks the most stable, I think all platforms were
passing on this, 1407017 only passed on Ubuntu jdk6, nothing else.
If we can confirm 13737
On 29-11-12 13:07, Peter Firmstone wrote:
On 29/11/2012 10:04 PM, Simon IJskes - QCG wrote:
How about the following, we develop on a branch. Then we merge or
patch. We release. We pull a new branch of trunk. We merge/patch stuff
that did not make it in the release from the previous dev branch
On 29/11/2012 10:04 PM, Peter Firmstone wrote:
On 29/11/2012 9:54 PM, Simon IJskes - QCG wrote:
On 29-11-12 12:34, Peter Firmstone wrote:
Oh, BTW, when I turned off debugging I had 6 tests fail, then after
running again only 2 tests failed; my recent patches haven't solved
concurrency issues, d
On 29/11/2012 10:04 PM, Simon IJskes - QCG wrote:
On 29-11-12 12:34, Peter Firmstone wrote:
I think that's wise equally I'm pondering how you cope with trunk
moving on
and breaking a bunch of your tests for which there would be fixes in
the
trunk test suite. Are you happy doing merges as and
On 29-11-12 12:34, Peter Firmstone wrote:
I'm not sure, at this point I just know we've got problems, there's a
lot of coupling in the test suite and a lot of shared state; it's all
based on inheritance.
There are two test types:
1. Jini Standards Compliance
2. Implementation integration
On 29/11/2012 9:54 PM, Simon IJskes - QCG wrote:
On 29-11-12 12:34, Peter Firmstone wrote:
Oh, BTW, when I turned off debugging I had 6 tests fail, then after
running again only 2 tests failed; my recent patches haven't solved
concurrency issues, debugging masked it.
Sorry to hear that. I've s
On 29-11-12 12:34, Peter Firmstone wrote:
I think that's wise equally I'm pondering how you cope with trunk
moving on
and breaking a bunch of your tests for which there would be fixes in the
trunk test suite. Are you happy doing merges as and when or ???
I'm not sure, at this point I just k
On 29-11-12 12:34, Peter Firmstone wrote:
Oh, BTW, when I turned off debugging I had 6 tests fail, then after
running again only 2 tests failed; my recent patches haven't solved
concurrency issues, debugging masked it.
Sorry to hear that. I've seen a failure in discovery on a number of
occasio
On 29/11/2012 12:49 AM, Dan Creswell wrote:
It would be nice to have a stable qa suite branch for testing River
development and another for refactoring and developing the test suite
itself, without interfering with the development process of River. The
test suite requires maintenance too, but ri
10 matches
Mail list logo
