Hi all,
It probably is an issue with the tests, but, the problem is that we can't
reproduce them locally in our setups for some reason (its either the JDK
version, either the type of machine or something) that introduces some
randomness. This is why I was concerned about cleaning up a lot, just to
Senaka, Bamboo doesn't do anything differently. It is dumb & just calls
Maven. What you are seeing is an issue in the tests.
--
Afkham Azeez
Sent from my phone
On Apr 3, 2012 11:55 AM, "Senaka Fernando" wrote:
> Hi all,
>
> Thanks for creating this issue. We are recompiling the entire trunk on a
On Tue, Apr 3, 2012 at 11:54 AM, Senaka Fernando wrote:
> Hi all,
>
> Thanks for creating this issue. We are recompiling the entire trunk on a
> clean repo, which the builder does not do; and will double check on these
> issues. Srinath, it has to connect to the internet to do a schema import
> f
Hi all,
Thanks for creating this issue. We are recompiling the entire trunk on a
clean repo, which the builder does not do; and will double check on these
issues. Srinath, it has to connect to the internet to do a schema import
from URL (we have disabled file URLs and we can't enable that just to
On Tue, Apr 3, 2012 at 8:54 AM, Charith Wickramarachchi
wrote:
>
>
> On Tue, Apr 3, 2012 at 8:52 AM, Selvaratnam Uthaiyashankar
> wrote:
>>
>> On Tue, Apr 3, 2012 at 8:50 AM, Charith Wickramarachchi
>> wrote:
>> > Hi Senaka ,
>> >
>> > Last night I commented out this test case and triggered a bu
On Tue, Apr 3, 2012 at 8:52 AM, Selvaratnam Uthaiyashankar wrote:
> On Tue, Apr 3, 2012 at 8:50 AM, Charith Wickramarachchi
> wrote:
> > Hi Senaka ,
> >
> > Last night I commented out this test case and triggered a build starting
> > from Kernel. Please find the Blocker created for this in [1]
>
On Tue, Apr 3, 2012 at 8:50 AM, Charith Wickramarachchi
wrote:
> Hi Senaka ,
>
> Last night I commented out this test case and triggered a build starting
> from Kernel. Please find the Blocker created for this in [1]
>
> [1]https://wso2.org/jira/browse/REGISTRY-718
Charith,
This issue should go
Hi Senaka ,
Last night I commented out this test case and triggered a build starting
from Kernel. Please find the Blocker created for this in [1]
[1]https://wso2.org/jira/browse/REGISTRY-718
thanks,
Charith
On Tue, Apr 3, 2012 at 2:50 AM, Senaka Fernando wrote:
> Hi Dimuthu,
>
> If you checke
What does the test do? Why does it connect to the internet?
if the test is prone to errors (e.g. connect to internet) we should
change that .. harm of tests that are prone to errors is great as it
waste valuable time
--Srinath
On Tue, Apr 3, 2012 at 2:50 AM, Senaka Fernando wrote:
> Hi Dimuthu
Hi Dimuthu,
If you checked on the latest packs, the test is passing on Bamboo right
now. This should be an intermittent connection issue (or something related)
when fetching the schemas.
Thanks,
Senaka.
On Mon, Apr 2, 2012 at 11:02 PM, Dimuthu Leelarathne wrote:
> Hi,
>
> Please have a look at
Hi,
Please have a look at this and provide a solution. If you can't find a
proper solution soon, let's comment out the test case and create a L1 for
it.
thanks,
dimuthu
On Mon, Apr 2, 2012 at 2:31 PM, Afkham Azeez wrote:
> Just got through the test code, and think about the cases in which this
On Apr 2, 2012 2:32 PM, "Afkham Azeez" wrote:
>
> Just got through the test code, and think about the cases in which this
assertion failure can occur. Don't be hasty to blame Bamboo. If there are
threading issues, they may manifest on some environments but not others.
Agree with you!!
Thanks.
/H
Just got through the test code, and think about the cases in which this
assertion failure can occur. Don't be hasty to blame Bamboo. If there are
threading issues, they may manifest on some environments but not others.
On Mon, Apr 2, 2012 at 2:15 PM, Senaka Fernando wrote:
> Hi Pradeep,
>
> It i
On Mon, Apr 2, 2012 at 2:15 PM, Senaka Fernando wrote:
> Hi Pradeep,
>
> It is not intermittent. But, how is this not reproducible locally? And,
> how did this just start happening without any changes to the code?
> Subash/Vijitha are working on a build of the whole platform on a clean
> repo. We
Hi
I went through the log of build #26 and saw all the products were passing
including GREG with tests. (Yes, Bamboo hasn't parsed the test results but
the builds were successful) That's why I was thinking there should be
something wrong in the test. Sorry for the noise.
Regards,
SanjayaV.
On M
Hi Pradeep,
It is not intermittent. But, how is this not reproducible locally? And, how
did this just start happening without any changes to the code?
Subash/Vijitha are working on a build of the whole platform on a clean
repo. We'll be able to make a decision on the reliability of Bamboo after
th
Hi,
we had a config issue in bamboo. This is not intermittent. Someone has to
fix it. Yes bamboo is reliable.
--Pradeep
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
How can an assertion fail intermittently?
java.lang.AssertionError: expected:<3> but was:<2>
at org.testng.Assert.fail(Assert.java:89)
at org.testng.Assert.failNotEquals(Assert.java:489)
at org.testng.Assert.assertEquals(Assert.java:118)
at org.testng.Assert.assert
Hi Sanjaya,
No it is not an intermittent failure. Its an all or nothing kind of a test
and there is no possibility of the behavior being random provided that the
clean up happened properly.
Thanks,
Senaka.
On Mon, Apr 2, 2012 at 2:07 PM, Sanjaya Vithanagama wrote:
> Hi Senaka,
>
> I just checke
Hi Senaka,
I just checked the last successful build (#26) log available at [1]. In
that all the 229 test cases of GREG has passed. So this must be an
intermittent failure?
[1]
http://builder4.us1.wso2.org:/bamboo/download/WSO2CARBON-PRODUCTS-JOB1/build_logs/WSO2CARBON-PRODUCTS-JOB1-26.log
R
And may I ask how did this fail without nobody committing anything after
the last series of builds that passed? Is Bamboo taking proper SVN updates
always? Or are we looking at some test log that is inconsistent each day?
I'd like if someone can pay attention into how Bamboo takes SVN updates and
d
Hi,
who is working on this test failure ?
--Pradeep
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
---
WSO2 Carbon > Products > #28 failed.
---
This build was manually triggered by BambooBuilder.
1/467 tests failed.
http://builder4.us1.wso2.org:/bamboo/bro
23 matches
Mail list logo
