I've just made some very minor changes to a website, the code now wont deploy...no obvious errors in the build log - although the log appears to be in a great deal more detail than previous builds and looks to have been cut shoty
ssa.apphb.com
I've just made some very minor changes to a website, the code now wont deploy...no obvious errors in the build log - although the log appears to be in a great deal more detail than previous builds and looks to have been cut shoty
ssa.apphb.com
Discussions are closed to public comments.
If you need help with AppHarbor please
start a new discussion.
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
#1 Posted by Dakuan on 05 Jul, 2011 03:36 PM
*short, rather.
#2 Posted by Dakuan on 05 Jul, 2011 05:47 PM
further to that, i've re-pushed the previous successful build - now won't build either!
#3 Posted by friism Support staff on 05 Jul, 2011 08:35 PM
What is the error your are getting? Also, if possible, please invite [email blocked] as a collaborator. That way, we can take a look at the log.
Michael
#4 Posted by Dakuan on 06 Jul, 2011 08:00 AM
Hi Michael,
Thanks for getting back to me....There aren't any build errors, at least not on the part of the log I can see.
Have added you as a collaborator.
Cheers,
Dom
#5 Posted by friism Support staff on 07 Jul, 2011 06:12 AM
Our test-runner (Gallio) seems to have problems inspecting the SharpArch fll that you are referencing (due to a missing NHiberta.Validator refrence). We are looking for a resolution.
#6 Posted by Dakuan on 07 Jul, 2011 09:34 AM
cool, removing that reference has worked for now :)
#7 Posted by friism Support staff on 07 Jul, 2011 10:46 PM
The problem with your builds is that you reference SharpArch.dll. That has a dependency on NHibernate.Validator which you are not referencing. This causes an an assembly-binding exception when our test-runner tries to load the SharpArch.dll to determine whether it contains any unit tests. For now, please include the missing dll and see whether that solves the problem.
We are trying to figure how to better report problems like these (no easy solution presents itself right now).
friism closed this discussion on 07 Jul, 2011 10:46 PM.