Hi Monty,
Thanks for your reply (and your intention to fix this).
On 06/30/2013 03:26 AM, Monty Taylor wrote:
Are you seeing problems with anything other than
glance-manage?
As much as I can see, the only other unit tests that failed for b1 in
Debian are:
Hi Thomas,
We switched to using entrypoints for creating our binaries. Unfortunately,
this means you need to have the glance version installed in some sense in
your path when you want to run those tests. This felt like a no-no when we
made the change, but it worked fine without any changes to our
On 06/30/2013 12:16 AM, Mark Washenberger wrote:
Hi Thomas,
We switched to using entrypoints for creating our binaries.
Can you explain this a bit more?
Unfortunately, this means you need to have the glance version
installed in some sense in your path when you want to run those tests.
On 06/29/2013 02:14 PM, Thomas Goirand wrote:
On 06/30/2013 12:16 AM, Mark Washenberger wrote:
Hi Thomas,
We switched to using entrypoints for creating our binaries.
Can you explain this a bit more?
Unfortunately, this means you need to have the glance version
installed in some sense in
Munging together some replies:
On Sat, Jun 29, 2013 at 12:26 PM, Monty Taylor mord...@inaugust.com wrote:
On 06/29/2013 02:14 PM, Thomas Goirand wrote:
On 06/30/2013 12:16 AM, Mark Washenberger wrote:
Hi Thomas,
We switched to using entrypoints for creating our binaries.
Can you
I believe we should fix the unittests to not shell out to glance-manage
in that manner. One of the nice things about moving the code from bin/
to glance.cmd is that it's available inside of the source tree for
unittests! :) What we want to do is call the glance.cmd.manage:main()
function
On 06/29/2013 08:02 PM, John Bresnahan wrote:
I believe we should fix the unittests to not shell out to glance-manage
in that manner. One of the nice things about moving the code from bin/
to glance.cmd is that it's available inside of the source tree for
unittests! :) What we want to do is
