[pony-build] Problems with build-nose (was: reminder: blog posts etc.)
C. Titus Brown
ctb at msu.edu
Sat Feb 13 19:41:43 PST 2010
On Sat, Feb 13, 2010 at 02:44:55PM -0600, Khushboo Shakya wrote:
> I have pushed the code to github to the nose_problems branch. However I
> still don't see in github. It does show in my computer that the file has
> been pushed though.
OK, I see some of the issues...
There are a couple of problems, some big and some small.
First, you've deleted everything in the pony-build archive except the
client code, and moved the client code into the main directory. For example,
http://github.com/kshakya/pony-build/blob/nose_problems/pony_client.py
should be under client/, as in
http://github.com/ctb/pony-build/blob/master/client/pony_client.py
I think the simplest thing for you to do is to get your client code working,
and then trash this branch and start over from a clean checkout of my
master branch. I can walk you through that once you're ready.
In the meantime, you can focus on getting the client code working :).
So, there, I have two requests:
- can you list the commands that you would run on the command line to:
check out the latest version of nose
build it
run the tests
What happens when you run those commands?
Remember, pony-build is just running those commands, within a particular
context (or Context); so if you're getting an error, you should first be
sure that it's not an error in your understanding of what should be running.
(Hint: this is at least one of your problems.)
- you're running into problems with 'assert 0', which is a fencepost
put in the HgCheckout code by me in order to flag an unexpected error
that I didn't want to handle. Conveniently, you have the source code
surrounding the assert -- what condition is triggering the assert?
What exactly is the code looking for? Now look at your answers to my
first request and see if anything looks out of whack.
cheers,
--titus
More information about the pony-build
mailing list