brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rdowner <>
Subject [GitHub] incubator-brooklyn pull request: More fixes to release blockers
Date Fri, 26 Jun 2015 11:51:12 GMT
Github user rdowner commented on the pull request:
    Relevant discussion from IRC channel, for the record:
    [12:00:39]  <alexheneveld>	richardasf: do you have a jenkins failure for the RebindFeedTest
failure you’ve marked WIP ?
    [12:01:20]  <alexheneveld>	i haven’t noticed that one failing, and it’s a good
test to have enabled
    [12:02:06]  <richardasf>	No ... but I'm getting it pretty consistently 50% of the
time on my release build env - an Ubuntu VirtualBox VM on my Mac. Error is that it expected
1 but got 6 or 8
    [12:02:47]  <richardasf>	(it must be a rather unique environment for it to never
show up on Jenkins)
    [12:03:36]  <alexheneveld>	aha there has been one jenkins failure -
    [12:03:37]  <svet>	I also see it failing on a Ubuntu VM. Also consistently failing
on the windows build
    [12:03:44]  <richardasf>$brooklyn-core/#showFailuresLink
    [12:04:07]  <svet>	(consistent as in 100%)
    [12:04:10]  <richardasf>	Yep svet there it is failing on the Windows build - our
canary-in-the-coalmine for tests on the edge :)
    [12:04:33]  <alexheneveld>	odd.  can we WIP that test on an 0.7.0 branch only?
    [12:04:54]  <richardasf>	Yes we can do that
    [12:05:20]  <alexheneveld>	thx - there’s a fair chance points to a rebind problem
in those environments, rather than just a bad test
    [12:06:57]  <richardasf>	Would you say that this test failure is important? It should
be investigated further before releasing? Concerned that your statement suggests that Ubuntu
VMs have a problem with rebind...
    [12:22:40]  <alexheneveld>	no, shouldn’t block release — it’s a fringe issue,
if persistence of feeds is on, you might get duplication of feeds.
    [12:22:44]  <alexheneveld>	richardasf: ^^^

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message