Message-
From: Marcus [mailto:shadow...@gmail.com]
Sent: 16 October 2014 18:08
To: dev@cloudstack.apache.org
Subject: Re: master broken
Wouldn't it have to be pushed first to pass any CI testing? So in theory we
should never have CI catch compile errors if we don't push code that won't
compile.
t find
> > BaremetalProvisionDoneNotificationCmd in any of the commits. But this is
> > only one of problems I think.
> >
> >
> >
> >>
> >> > -Original Message-----
> >> > From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> &g
t; -Original Message-
>> > From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
>> > Sent: Thursday, October 16, 2014 2:28 PM
>> > To: dev; Frank Zhang
>> > Subject: Re: master broken
>> >
>> > I can't seem to get it working by rever
> > To: dev; Frank Zhang
> > Subject: Re: master broken
> >
> > I can't seem to get it working by reverting, neither the merge commit nor
> > individual related commits.
> >
> > @Frank: can we disable baremetal all together until you are done?
> >
ang
> Subject: Re: master broken
>
> I can't seem to get it working by reverting, neither the merge commit nor
> individual related commits.
>
> @Frank: can we disable baremetal all together until you are done?
>
> On Thu, Oct 16, 2014 at 9:43 PM, Daan Hoogland
&
I can't seem to get it working by reverting, neither the merge commit nor
individual related commits.
@Frank: can we disable baremetal all together until you are done?
On Thu, Oct 16, 2014 at 9:43 PM, Daan Hoogland
wrote:
> I found some culprits, it is in partly reverted code that was committed
I found some culprits, it is in partly reverted code that was committed
before the cut of master and 4.5. All to do with Baremetal. I am having a
look.
On Thu, Oct 16, 2014 at 8:54 PM, Daan Hoogland
wrote:
> On Thu, Oct 16, 2014 at 8:17 PM, Marcus wrote:
>
>> I mean as they are ordered in the
On Thu, Oct 16, 2014 at 8:17 PM, Marcus wrote:
> I mean as they are ordered in the log. The commits before and after the
> merge are both working points.
>
We are talking about a merge of master and 4.5, so I am now trying 4.5 to
see if the errors are in there as well. If they are I will fix th
I mean as they are ordered in the log. The commits before and after the
merge are both working points.
commit 20d3cf1acc535c3380e52e92a4108444a0b593e3
Author: Alex Brett
Date: Wed Oct 15 18:50:57 2014 +0100
CLOUDSTACK-7727 Skip various BVT tests on LXC
A number of BVT tests are not va
what do you mean by just after the merge?
On Thu, Oct 16, 2014 at 7:28 PM, Marcus wrote:
> The commit just before and just after the merge seem to work. They're both
> from the 15th.
>
>
> On Thu, Oct 16, 2014 at 11:12 AM, Nguyen Anh Tu wrote:
>
> > I've just tried the commit before HEAD. It wo
The commit just before and just after the merge seem to work. They're both
from the 15th.
On Thu, Oct 16, 2014 at 11:12 AM, Nguyen Anh Tu wrote:
> I've just tried the commit before HEAD. It worked!
>
> --Tuna
>
> On Fri, Oct 17, 2014 at 12:10 AM, Daan Hoogland
> wrote:
>
> > Marcus did you try
I've just tried the commit before HEAD. It worked!
--Tuna
On Fri, Oct 17, 2014 at 12:10 AM, Daan Hoogland
wrote:
> Marcus did you try the commit just before the merge? given the location of
> the problem it might well be in the vpc refactor work or a combination of
> the both.
>
> I am trying m
Marcus did you try the commit just before the merge? given the location of
the problem it might well be in the vpc refactor work or a combination of
the both.
I am trying myself as well now
On Thu, Oct 16, 2014 at 7:07 PM, Marcus wrote:
> I can't rule out that it's specific to me at the moment
I can't rule out that it's specific to me at the moment, but I cleaned my
repo and rebuilt with the same failure, then went back to the commit just
before this and it succeeded.
Wouldn't it have to be pushed first to pass any CI testing? So in theory we
should never have CI catch compile errors if
Yes, I get the same error.
--Tuna
On Fri, Oct 17, 2014 at 12:03 AM, Daan Hoogland
wrote:
> On Thu, Oct 16, 2014 at 6:57 PM, Marcus wrote:
>
> > We probably shouldn't be
> > pushing code into the repo that we haven't tried to compile.
> >
>
> as I understand it it passed travis, I agree other
On Thu, Oct 16, 2014 at 6:57 PM, Marcus wrote:
> We probably shouldn't be
> pushing code into the repo that we haven't tried to compile.
>
as I understand it it passed travis, I agree otherwise
--
Daan
unsubscribe
-Original Message-
From: Rayees Namathponnan [mailto:rayees.namathpon...@citrix.com]
Sent: Wednesday, October 16, 2013 4:09 PM
To: dev@cloudstack.apache.org
Subject: RE: Master broken in KVM ?
KVM Master automation runs blocked due to defect
https://issues.apache.org/jira
KVM Master automation runs blocked due to defect
https://issues.apache.org/jira/browse/CLOUDSTACK-4865
Regards,
Rayees
-Original Message-
From: Prasanna Santhanam [mailto:t...@apache.org]
Sent: Monday, October 14, 2013 10:32 PM
To: dev@cloudstack.apache.org
Subject: Re: Master broken
The actual error was a few lines above what Rayees indicated. I've
filed a bug report in CLOUDSTACK-4865. All the deployVM commands are
failing.
On Tue, Oct 15, 2013 at 10:47:45AM +0530, Prasanna Santhanam wrote:
> well deployment was broken but i fixed it over the weekend. this was
> the configde
well deployment was broken but i fixed it over the weekend. this was
the configdepot changes that puts the 'host' variable in the agent set
to localhost causing the kvm agent to reach back to itself.
the vm deployment failures i am investigating. the deployvm api always
shows XenServer because the
Seems to work. I was able to deploy a VM from the UI at least, so
something in the test perhaps is wrongly choosing hypervisor when
constructing the API call.
This was master as of:
commit 8b397f1d427b9e8704ab684cf3c359e5d35e8d91
Author: Jessica Wang
Date: Mon Oct 14 13:39:27 2013 -0700
On Mon
I can pull down the latest and give it a shot. It was working for me
earlier. Could this be the automation run or test config's fault?
On Mon, Oct 14, 2013 at 3:28 PM, Rayees Namathponnan
wrote:
> Is it master broken in KVM ?
>
> All deployment failed in KVM master automation run, result availab
On Fri, Jun 28, 2013 at 05:38:19PM +, Edison Su wrote:
> Devcloud has a trick to clean up systemvm.iso:
> There is a bug in xapi on Ubuntu/debian(not sure the bug still there
> in the latest debian or not), which can't attach an ISO to a VM. I
> worked around the bug by creating a VDI on primar
I did a mvn -Pdeveloper -Dsystemvm clean install and those
systemvm.iso(s) went away. So it must be within devcloud somewhere
that the iso existed.
On Fri, Jun 28, 2013 at 10:41:39AM -0700, Hugo Trippaers wrote:
> Hey Prasanna,
>
> I just did a quick test, these systemvm.iso files are generated
Hey Prasanna,
I just did a quick test, these systemvm.iso files are generated by the default
maven build (mvm -Dnonoss -Psystemvm install)
./client/target/cloud-client-ui-4.2.0-SNAPSHOT/WEB-INF/classes/vms/systemvm.iso
./client/target/generated-webapp/WEB-INF/classes/vms/systemvm.iso
./services/
a Santhanam [mailto:t...@apache.org]
> Sent: Friday, June 28, 2013 10:22 AM
> To: dev@cloudstack.apache.org
> Subject: Re: Master broken on systemVM start
>
> I deleted all traces of systemvm.iso from my codebase $ find . -name
> systemvm.iso | xargs -n1 rm -f
>
> Then reverte
I deleted all traces of systemvm.iso from my codebase
$ find . -name systemvm.iso | xargs -n1 rm -f
Then reverted my devcloud snapshot to old state and don't see this
error again.
I wonder by mvn doesn't do a good job of cleaning though :/
Thanks for the fixes to the bugs and the upcoming fixes
Prasanna, glad to know that CLOUDSTACK-3137 is resolved. I fixed
CLOUDSTACK-3249 yesterday for a corner case reported by Alena, but I could
not reproduce CLOUDSTACK-3137 on my environment at all. For the JSON
issue, I can only tell that it is inconsistent systemvm issue between
management server an
On Fri, Jun 28, 2013 at 12:17:55PM +0530, Prasanna Santhanam wrote:
> On Tue, Jun 25, 2013 at 04:07:08PM +, Min Chen wrote:
> > Json deserialization issue is caused by out-of-dated systemvm.iso on your
> > hypervisor host. You need rebuilding systemvm.iso and deployed to your
> > hypervisor hos
On Tue, Jun 25, 2013 at 04:07:08PM +, Min Chen wrote:
> Json deserialization issue is caused by out-of-dated systemvm.iso on your
> hypervisor host. You need rebuilding systemvm.iso and deployed to your
> hypervisor host.
>
CLOUDSTACK-3137 exists and seems to be a problem with HA and
systemVM
Json deserialization issue is caused by out-of-dated systemvm.iso on your
hypervisor host. You need rebuilding systemvm.iso and deployed to your
hypervisor host.
Thanks
-min
On 6/25/13 12:03 AM, "Prasanna Santhanam" wrote:
>Just to be clear, the issue 3137 is related to systemVM HA and isn't
>r
Just to be clear, the issue 3137 is related to systemVM HA and isn't
related to the JSON serialization. The JSON serialization is probably
because you will need to upgrade your agent to the latest. I don't see
the problem with KVM, Xen and XCP on the test infrastructure.
On Tue, Jun 25, 2013 at 06
can't find
com.cloud.agent.api.com.cloud.agent.api.StartupRoutingCommand
at
com.cloud.agent.transport.ArrayTypeAdaptor.deserialize(ArrayTypeAdaptor.java:79)
at
com.cloud.agent.transport.ArrayTypeAdaptor.deserialize(ArrayTypeAdaptor.java:37)
at
com.google.gson.JsonDeserializerExceptionWrapper.deserialize(JsonDeserializerExc
1 , I am getting it too !
> >
> >-Original Message-
> >From: Sanjay Tripathi [mailto:sanjay.tripa...@citrix.com]
> >Sent: Tuesday, June 25, 2013 12:03 PM
> >To: dev@cloudstack.apache.org
> >Subject: RE: Master broken on systemVM start
> >
> >I am also g
ipathi [mailto:sanjay.tripa...@citrix.com]
>Sent: Tuesday, June 25, 2013 12:03 PM
>To: dev@cloudstack.apache.org
>Subject: RE: Master broken on systemVM start
>
>I am also getting this exception on latest master:
>
>WARN [utils.nio.Task] (AgentManager-Handler-2:
+1 , I am getting it too !
-Original Message-
From: Sanjay Tripathi [mailto:sanjay.tripa...@citrix.com]
Sent: Tuesday, June 25, 2013 12:03 PM
To: dev@cloudstack.apache.org
Subject: RE: Master broken on systemVM start
I am also getting this exception on latest master:
WARN
I am also getting this exception on latest master:
WARN [utils.nio.Task] (AgentManager-Handler-2:) Caught the following exception
but pushing on
com.google.gson.JsonParseException: The JsonDeserializer
com.cloud.agent.transport.ArrayTypeAdaptor@18e6ae2 failed to deserialize json
object
[{"Sta
ginal Message-
>> From: Rajesh Battala [mailto:rajesh.batt...@citrix.com]
>> Sent: Friday, April 12, 2013 8:32 PM
>> To: dev@cloudstack.apache.org
>> Subject: RE: Master broken
>>
>> +1 It would be very nice to see a wiki page how to write unit test. It
>>wo
Rajesh Battala [mailto:rajesh.batt...@citrix.com]
> Sent: Friday, April 12, 2013 8:32 PM
> To: dev@cloudstack.apache.org
> Subject: RE: Master broken
>
> +1 It would be very nice to see a wiki page how to write unit test. It would
> be
> great help.
>
> Thanks
>
+1 It would be very nice to see a wiki page how to write unit test. It would be
great help.
Thanks
Rajesh Battala
> -Original Message-
> From: Chip Childers [mailto:chip.child...@sungard.com]
> Sent: Friday, April 12, 2013 7:57 PM
> To: dev@cloudstack.apache.org
> Subj
On Thu, Apr 11, 2013 at 05:57:01PM -0700, Kelven Yang wrote:
> These issues are caused by that some of components are not really mocked,
> instead, they are loaded directly main source.
>
> One of the benefits from Spring is that it integrates with Mokito nicely,
> all we need is to probably have
To: dev@cloudstack.apache.org
>> Subject: Re: Master broken
>>
>> On Mon, Apr 08, 2013 at 07:44:41AM +, Hugo Trippaers wrote:
>> >
>> >
>> > > -Original Message-
>> > > From: Chip Childers [mailto:chip.child...@sungard.com]
>
> -Original Message-
> From: Chip Childers [mailto:chip.child...@sungard.com]
> Sent: Monday, April 08, 2013 3:51 PM
> To: dev@cloudstack.apache.org
> Subject: Re: Master broken
>
> On Mon, Apr 08, 2013 at 07:44:41AM +, Hugo Trippaers wrote:
> >
>
On Mon, Apr 08, 2013 at 07:44:41AM +, Hugo Trippaers wrote:
>
>
> > -Original Message-
> > From: Chip Childers [mailto:chip.child...@sungard.com]
> > Sent: Saturday, April 06, 2013 7:16 PM
> > To: dev@cloudstack.apache.org
> > Subject: Re: Master
> -Original Message-
> From: Chip Childers [mailto:chip.child...@sungard.com]
> Sent: Saturday, April 06, 2013 7:16 PM
> To: dev@cloudstack.apache.org
> Subject: Re: Master broken
>
> On Sat, Apr 06, 2013 at 05:27:11AM +, Prasanna Santhanam wrote:
> > Ah
21 AM
> To: dev@cloudstack.apache.org
> Subject: RE: Master broken
>
> > That will be hard to do since the checkin test requires the DB to be
> > present as
> > it starts up the server and sets-up the databases. We'd have to turn it off
> > for
> > the build
-
From: Alex Huang [mailto:alex.hu...@citrix.com]
Sent: Saturday, April 06, 2013 05:21 AM
To: dev@cloudstack.apache.org
Subject: RE: Master broken
> That will be hard to do since the checkin test requires the DB to be present
> as
> it starts up the server and sets-up the databases.
Sent from my iPhone
On 5 apr. 2013, at 23:21, "Alex Huang" wrote:
>> That will be hard to do since the checkin test requires the DB to be present
>> as
>> it starts up the server and sets-up the databases. We'd have to turn it off
>> for
>> the build and turn it back on again for the bvt. Be
> That will be hard to do since the checkin test requires the DB to be present
> as
> it starts up the server and sets-up the databases. We'd have to turn it off
> for
> the build and turn it back on again for the bvt. Best if we avoid doing -
> DskipTests when building as a general good rule.
I
On 4 April 2013 05:15, Alex Huang wrote:
> Prasanna,
>
> This is actually a very interesting case. In our check-in test, is there any
> way for us to disable db access when running the unit tests? I can see that
> this would be one of the things that the developer can easily forget but hits
>
often.
Thanks.
--Alex
> -Original Message-
> From: Kelven Yang [mailto:kelven.y...@citrix.com]
> Sent: Wednesday, April 3, 2013 11:23 AM
> To: Hugo Trippaers; Alena Prokharchyk; dev@cloudstack.apache.org;
> cloudstack-...@incubator.apache.org
> Subject: Re: Master broken
t;> -Original Message-
>> From: Kelven Yang [mailto:kelven.y...@citrix.com]
>> Sent: Tuesday, April 02, 2013 7:41 PM
>> To: Alena Prokharchyk; dev@cloudstack.apache.org; cloudstack-
>> d...@incubator.apache.org; Hugo Trippaers
>> Subject: Re: Master br
essage-
> From: Kelven Yang [mailto:kelven.y...@citrix.com]
> Sent: Tuesday, April 02, 2013 7:41 PM
> To: Alena Prokharchyk; dev@cloudstack.apache.org; cloudstack-
> d...@incubator.apache.org; Hugo Trippaers
> Subject: Re: Master broken
>
> I've applied a commit 5782abf8f
>>-Original Message-
>>From: Hugo Trippaers [mailto:htrippa...@schubergphilis.com]
>>Sent: Tuesday, April 02, 2013 1:37 PM
>>To: dev@cloudstack.apache.org; cloudstack-...@incubator.apache.org
>>Subject: RE: Master broken
>>
>>Thanks Pranav,
>&
t;Pranav
>
>-Original Message-
>From: Hugo Trippaers [mailto:htrippa...@schubergphilis.com]
>Sent: Tuesday, April 02, 2013 1:37 PM
>To: dev@cloudstack.apache.org; cloudstack-...@incubator.apache.org
>Subject: RE: Master broken
>
>Thanks Pranav,
>
>
stack-...@incubator.apache.org
Subject: RE: Master broken
Thanks Pranav,
I couldn't find an easy way to fix the test so I indeed disabled it. See commit
df6b97c194caa8b34fa14bf5164eb2fe1f26b2b1.
Raised a ticket for Kelven (CLOUDSTACK-1884) to have a look at it.
Cheers,
Hugo
> -Ori
:pranav.sax...@citrix.com]
> Sent: dinsdag 2 april 2013 10:04
> To: dev@cloudstack.apache.org; cloudstack-...@incubator.apache.org
> Subject: RE: Master broken
>
> This commit deals with the tests for create network offering - Commit:
> 5782abf8f80fce929e3d6e20068bc165f2360426 and I a
This commit deals with the tests for create network offering - Commit:
5782abf8f80fce929e3d6e20068bc165f2360426 and I am presuming because of this
only the test is failing.
You might need to revert the commit if required.
Thanks,
Pranav
-Original Message-
From: Hugo Trippaers [mailto:
58 matches
Mail list logo
