5:07 a.m.
Hi,
The processor id changed to domanin_name/proc, then does the libvirt-cim
rpm
for Fedora 9 will reflect this recent changes? If so, when is it time
to replace? Also the same issues in terms of MB versus KB for memory.
I'm not sure if libvirt-cim rpm freezed, then how cimtest are represent?
Do we have to branch cimtest into two parts, one for libvirt-cim rpm,
the other for recent provider changes?
Thanks!
Best,
Regards
Daisy Guo Lian Yun
E-mail: yunguol(a)cn.ibm.com
IBM China Development Lab, Shanghai, China
TEL: (86)-21-61008057
5:59 p.m.
GY> The processor id changed to domanin_name/proc, then does the
GY> libvirt-cim rpm for Fedora 9 will reflect this recent changes? If
GY> so, when is it time to replace? Also the same issues in terms of
GY> MB versus KB for memory. I'm not sure if libvirt-cim rpm freezed,
GY> then how cimtest are represent? Do we have to branch cimtest into
GY> two parts, one for libvirt-cim rpm, the other for recent provider
GY> changes?
This is a good point. The Fedora 9 RPM has been unchanged for a while
now, so none of the changes that you mention are included. I think
that the test development should proceed to track the libvirt-cim
development tree, but perhaps there is a way that we can map FAIL to
XFAIL for older versions of the provider.
Does anyone have a suggestion for a reasonable way we could do this?
--
Dan Smith
IBM Linux Technology Center
Open Hypervisor Team
email: danms(a)us.ibm.com
7:26 p.m.
On Thu, Apr 10, 2008 at 08:59:27AM -0700, Dan Smith wrote:
GY> The processor id changed to domanin_name/proc, then does the
GY> libvirt-cim rpm for Fedora 9 will reflect this recent changes? If
GY> so, when is it time to replace? Also the same issues in terms of
GY> MB versus KB for memory. I'm not sure if libvirt-cim rpm freezed,
GY> then how cimtest are represent? Do we have to branch cimtest into
GY> two parts, one for libvirt-cim rpm, the other for recent provider
GY> changes?
This is a good point. The Fedora 9 RPM has been unchanged for a while
now, so none of the changes that you mention are included. I think
Basically the Fedora-9 tree is frozen, but you should be able
to push update for it after it has been released
that the test development should proceed to track the libvirt-cim
development tree, but perhaps there is a way that we can map FAIL to
Well you could push dated release to rawhide but it can get tiring
quickly
Daniel
--
Red Hat Virtualization group http://redhat.com/virtualization/
Daniel Veillard | virtualization library http://libvirt.org/
veillard(a)redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/
8:10 p.m.
DV> Basically the Fedora-9 tree is frozen, but you should be able to
DV> push update for it after it has been released
Right, which I definitely plan to do. I'd like the ability to look at
a test report and see "X failures that have been fixed in the tree but
are not fixed on the current platform". That will help indicate when
a refresh to Fedora or a new release is a good idea. Might be a bit
of a lofty goal, though :)
--
Dan Smith
IBM Linux Technology Center
Open Hypervisor Team
email: danms(a)us.ibm.com
2:38 a.m.
Dan Smith wrote:
DV> Basically the Fedora-9 tree is frozen, but you should be able
to
DV> push update for it after it has been released
Right, which I definitely plan to do. I'd like the ability to look at
a test report and see "X failures that have been fixed in the tree but
are not fixed on the current platform". That will help indicate when
a refresh to Fedora or a new release is a good idea. Might be a bit
of a lofty goal, though :)
For future releases, would it be a good idea to archive the current
state of the cimtest tree at the same time a release is snapped of
libvirt-cim? This would allow us to preserve the state of the tests and
tie them to a given release.
This is a good point. The Fedora 9 RPM has been unchanged for a
while
now, so none of the changes that you mention are included. I think
that the test development should proceed to track the libvirt-cim
development tree, but perhaps there is a way that we can map FAIL to
XFAIL for older versions of the provider.
Does anyone have a suggestion for a reasonable way we could do this?
Have the test suite check for the libvirt-cim rpm. If it exists, grab
version. Otherwise, assume the providers are the most recent version
upstream.
If a test case needs to be updated due to a provider behavior change,
use an if condition based on the rpm version (or lack there of) to
determine the pass/fail/xfail behavior.
It's not a very elegant idea, but something along these lines might
work. And of course, such an idea wouldn't work on environments that
don't support rpm / that we currently don't build rpms for.
--
Kaitlin Rupert
IBM Linux Technology Center
kaitlin(a)linux.vnet.ibm.com
2:42 a.m.
KR> For future releases, would it be a good idea to archive the
KR> current state of the cimtest tree at the same time a release is
KR> snapped of libvirt-cim? This would allow us to preserve the state
KR> of the tests and tie them to a given release.
We can, and we could just use a tag for this. However, unless we get
closer to an all PASS/XFAIL situation, I'm not sure I see the point :)
KR> Have the test suite check for the libvirt-cim rpm. If it exists,
KR> grab version. Otherwise, assume the providers are the most recent
KR> version upstream.
Yeah, I dunno about that. We could definitely embed a version string
into one of the providers somewhere (i.e. VSMS) and key off of that.
We'd have to assume some base version if it doesn't exist (like for
what is in F9 now) of course.
--
Dan Smith
IBM Linux Technology Center
Open Hypervisor Team
email: danms(a)us.ibm.com
5:28 p.m.
Dan Smith wrote:
KR> For future releases, would it be a good idea to archive the
KR> current state of the cimtest tree at the same time a release is
KR> snapped of libvirt-cim? This would allow us to preserve the state
KR> of the tests and tie them to a given release.
We can, and we could just use a tag for this. However, unless we get
closer to an all PASS/XFAIL situation, I'm not sure I see the point :)
That's a good point.
KR> Have the test suite check for the libvirt-cim rpm. If it exists,
KR> grab version. Otherwise, assume the providers are the most recent
KR> version upstream.
Yeah, I dunno about that. We could definitely embed a version string
into one of the providers somewhere (i.e. VSMS) and key off of that.
We'd have to assume some base version if it doesn't exist (like for
what is in F9 now) of course.
When would you update the version string? Anytime a change goes into
libvirt-cim, there's a possibility that the change in behavior will
affect the test case. If you want to update a test so that it behaves
one way for libvirt releases older than x.x.4 and a different way for
releases x.x.4 and higher, then you'd need to update the embedded string
every time you check in a changeset. Unless I'm missing what you mean here.
Ideally, it'd be nice to use the hg changeset number, but I'm not sure
how to make that happen.
--
Kaitlin Rupert
IBM Linux Technology Center
kaitlin(a)linux.vnet.ibm.com
6:11 p.m.
KR> When would you update the version string? Anytime a change goes
KR> into libvirt-cim, there's a possibility that the change in
KR> behavior will affect the test case. If you want to update a test
KR> so that it behaves one way for libvirt releases older than x.x.4
KR> and a different way for releases x.x.4 and higher, then you'd need
KR> to update the embedded string every time you check in a changeset.
KR> Unless I'm missing what you mean here.
Well, I think it's probably appropriate to embed the actual version
number (i.e. 0.4) as well as the changeset number.
KR> Ideally, it'd be nice to use the hg changeset number, but I'm not
KR> sure how to make that happen.
There are ways :)
I'll see about a patch.
--
Dan Smith
IBM Linux Technology Center
Open Hypervisor Team
email: danms(a)us.ibm.com
6005
days inactive
6006
days old
7 comments
4 participants
participants (4)
-
Dan Smith -
Daniel Veillard -
Guo Lian Yun -
Kaitlin Rupert