What does your last patch fix? On Mon, Apr 6, 2009 at 1:00 PM, Henrik Feldt <[email protected]> wrote:
> Hello, > > > > <test-case name="Castle.ActiveRecord.Tests.ActiveRecordTestCase.FetchCount > " executed="True" success="False" time="0.704" asserts="10"> > > <failure> > > > <message><![CDATA[Castle.ActiveRecord.Framework.ActiveRecordException > : Could not perform ExecuteQuery for Blog > > ----> NHibernate.ADOException : could not execute query > > [ select count_big(*) as x0_0_ from BlogTable blog0_ where (na...@p0 ) ] > > Positional parameters: #0>hammett's blog > > [SQL: select count_big(*) as x0_0_ from BlogTable blog0_ where (na...@p0 )] > > ----> System.Data.SqlClient.SqlException : Invalid column name 'name'. > ]]></message> > > <stack-trace><![CDATA[at > Castle.ActiveRecord.ActiveRecordBase.ExecuteQuery(IActiveRecordQuery query) > in > c:\Dev\OSS\Castle-trunk3\ActiveRecord\Castle.ActiveRecord\Framework\ActiveRecordBase.cs:line > 763 > > at Castle.ActiveRecord.ActiveRecordBase.Count(Type targetType, String > filter, Object[] args) in > c:\Dev\OSS\Castle-trunk3\ActiveRecord\Castle.ActiveRecord\Framework\ActiveRecordBase.cs:line > 828 > > at Castle.ActiveRecord.Tests.Model.Blog.FetchCount(String filter, Object[] > args) in > c:\Dev\OSS\Castle-trunk3\ActiveRecord\Castle.ActiveRecord.Tests\Model\Blog.cs:line > 120 > > at Castle.ActiveRecord.Tests.ActiveRecordTestCase.FetchCount() in > c:\Dev\OSS\Castle-trunk3\ActiveRecord\Castle.ActiveRecord.Tests\ActiveRecordTestCase.cs:line > 545 > > --ADOException > > at NHibernate.Loader.Loader.DoList(ISessionImplementor session, > QueryParameters queryParameters) > > at NHibernate.Loader.Loader.ListIgnoreQueryCache(ISessionImplementor > session, QueryParameters queryParameters) > > at NHibernate.Loader.Loader.List(ISessionImplementor session, > QueryParameters queryParameters, ISet`1 querySpaces, IType[] resultTypes) > > at NHibernate.Hql.Classic.QueryTranslator.List(ISessionImplementor session, > QueryParameters queryParameters) > > at NHibernate.Engine.Query.HQLQueryPlan.PerformList(QueryParameters > queryParameters, ISessionImplementor session, IList results) > > at NHibernate.Impl.SessionImpl.List(String query, QueryParameters > queryParameters, IList results) > > at NHibernate.Impl.SessionImpl.List(String query, QueryParameters > parameters) > > at NHibernate.Impl.QueryImpl.List() > > at NHibernate.Impl.AbstractQueryImpl.UniqueResult() > > at Castle.ActiveRecord.Queries.CountQuery.InternalExecute(ISession session) > in > c:\Dev\OSS\Castle-trunk3\ActiveRecord\Castle.ActiveRecord\Framework\Queries\CountQuery.cs:line > 104 > > at > Castle.ActiveRecord.ActiveRecordBaseQuery.Castle.ActiveRecord.IActiveRecordQuery.Execute(ISession > session) in > c:\Dev\OSS\Castle-trunk3\ActiveRecord\Castle.ActiveRecord\Framework\Queries\ActiveRecordBaseQuery.cs:line > 83 > > at Castle.ActiveRecord.ActiveRecordBase.ExecuteQuery(IActiveRecordQuery > query) in > c:\Dev\OSS\Castle-trunk3\ActiveRecord\Castle.ActiveRecord\Framework\ActiveRecordBase.cs:line > 757 > > --SqlException > > at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, > Boolean breakConnection) > > at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException > exception, Boolean breakConnection) > > at > System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject > stateObj) > > at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand > cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet > bulkCopyHandler, TdsParserStateObject stateObj) > > at System.Data.SqlClient.SqlDataReader.ConsumeMetaData() > > at System.Data.SqlClient.SqlDataReader.get_MetaData() > > at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, > RunBehavior runBehavior, String resetOptionsString) > > at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior > cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async) > > at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior > cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, > DbAsyncResult result) > > at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior > cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) > > at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, > String method) > > at System.Data.SqlClient.SqlCommand.ExecuteDbDataReader(CommandBehavior > behavior) > > at System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader() > > at NHibernate.AdoNet.AbstractBatcher.ExecuteReader(IDbCommand cmd) > > at NHibernate.Loader.Loader.GetResultSet(IDbCommand st, Boolean > autoDiscoverTypes, Boolean callable, RowSelection selection, > ISessionImplementor session) > > at NHibernate.Loader.Loader.DoQuery(ISessionImplementor session, > QueryParameters queryParameters, Boolean returnProxies) > > at > NHibernate.Loader.Loader.DoQueryAndInitializeNonLazyCollections(ISessionImplementor > session, QueryParameters queryParameters, Boolean returnProxies) > > at NHibernate.Loader.Loader.DoList(ISessionImplementor session, > QueryParameters queryParameters) > > ]]></stack-trace> > > </failure> > > </test-case> > > > > I’ve set my db to case-sensitive to catch out bugs. That might be why. > > > > About the references… > > > > I don’t really understand what you mean. The references are for CLR 2.0 in > \SharedLibs\.net\2.0\ and previously they were in \build\net-2.0\ as you can > see if you look at my patch: > > > > > > - > <HintPath>..\..\build\net-2.0\debug\anrControls.Markdown.NET.dll</HintPath> > > + > <HintPath>..\..\SharedLibs\mono\anrControls.Markdown.NET.dll</HintPath> > > > > The minus; doesn’t that mean that I removed it and added the other? > Obviously all 3.5 assemblies are 2.0 CLR... > > > > The only thing that’s relevant in “How to build.txt” is “Use the command > build”. Surely it’s better if we can use nant and not tie it to cmd.exe (so > that even mono-people can build). > > > > If we look at the lines > > > > - <HintPath>..\..\SharedLibs\net\3.5\NHibernate.dll</HintPath> > > + <HintPath>..\..\SharedLibs\net\2.0\NHibernate.dll</HintPath> > > > > Surely it’s a problem, that there’s no NHibernate.dll in /net/3.5/-folder? > > > > Also, I wasn’t aware NHibernate has dependencies on System.Core or some > other 3.5 assembly, so why would it be in 3.5? (unless of course it _*has*_ > taken such a dependency, I haven’t checked in detail). > > > > “Are you using NUnit 2.*2*.x” – Yes, that’s what my patch fixed by default > with nant. Henry already said this, too. I just can’t see why you don’t > script it in the .build file rather than the build.cmd, which is why I > scripted it in the build file, so now it works both ways. > > > > Anyways. > > Henrik > > > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Roelof Blom > *Sent:* den 6 april 2009 10:59 > *To:* [email protected] > *Subject:* Re: Problems building, priorities of facilities. > > > > Henrik, > > > I've not applied your patch as it seems to depend on a .NET 2.0 build, we > are only supporting .NET 3.5 on the trunk so references to build\net-2.0 are > invalid. > > Some further answers inline > > -- Roelof. > > On Mon, Apr 6, 2009 at 1:06 AM, Henrik Feldt <[email protected]> wrote: > > Hello, > > > > Boldness added for your convenience to speed up reading ;). > > > > Problems building: > > 1. ActiveRecord tests, by *default SQL Server 2008* doesn’t like > some of *the syntax around “name*”. I haven’t changed anything here, so I > mostly just disable that test case, but I guess I could select the correct > dialect and make it work. > > What's the error? I am running AR tests successfully on SQL Server 2008. > > 2. > Castle.Facilities.Remoting.Tests.ConfigurableRegistrationTestCase.ClientContainerConsumingRemoteComponents > fails with System.*AppDomainUnloadedException*: Attempted to access an > unloaded AppDomain. > All the rest of the test-cases after this also fail. The interesting thing > here is how *there’s a .txt saying that facility has moved to > MicroKernel.Facilities *when, clearly obviously it hasn’t had its > housewarming party yet, *but is still getting tested.* I added a *property > in the build configuration file to disable testing* of that facility till > it supposedly gets removed: deadremoting.test, so I can disable it when > testing the rest. Running the rest of the tests afterwards succeed. What’s > the status on this? *Should I delete the old one and send a patch*?? > > Are you using NUnit 2.*2*.x (preferably where x=10), NUnit 2.4.x is known > to cause problems with appdomain stuff. Using our build.cmd (in the root > folder) will setup things for the correct versions of NAnt and Nunit. > > 3. When opening the solution in VS2008, there are 3-4 places *where > libs have been referenced from GAC*, where I try not to place these libs > which keep getting updated – anrControls, NHibernate and Boo.Lang .. Parser > .. Compiler in some of the project. I fixed this on trunk and referenced > from SharedLibs instead. Also NVelocity, *I couldn’t find in the > NVelocity.dll file in the SharedLibs*; why? So I added it there. I’m > submitting a *patch* for this in *this e-mail*. Furthermore, the > *BrailTestSite > isn’t signed by default* which causes an *exception* when running the *brail > tests*. Looking in the solution, *there’s no link the CastleKey.sln.* I > added a link to this key and tried the tests again (after first rebuilding > the projects individually) *and it passes then*. > > NVelocity isn't in SharedLibs because it's produced by the build. Please > read 'How to build.txt'. > > 4. WcfFacility *fails* because I need to start a *NetTcpPortSharing > * (according to the exception message), so I guess I have to start that. > However, I’m not using that facility either, so I added exactly the same > switch as in remoting, albeit renamed, in the default.build file there, so > *I can disable testing of it.* > > 5. When disabling the above, I can build and all is good, *all tests > pass*. (so I run; nant –D:activerecord.test=false > –D:deadremoting.test=false -D:wcfintegration.test=false) > > > > Other things: > > 1. I’ve created a component installer which allows you to *specify > priorities when installing facilities*. I did this because when I launch > my own facilities, they had some dependencies on the components of each > other, however, as far as I could see there was no feature in the kernel to > do this. Should I *add it into the trunk* and send a patch? The question > here is also, is there *anyone who wants it*? > > 2. What did you guys think about the FileTransaction I mailed about > before? Sending mail to *Ernst Naezer bounced* when using his e-mail he’s > using for this list. Does anybody *have his e-mail* so I can talk to him > directly? > > *3.* *Is there a release coming soon?* > > Cheers, > > Henke > > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en -~----------~----~----~----~------~----~------~--~---
