Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CA-142451: Unit tests #211

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

fquesnel
Copy link

Covering changes related to CA-142451.

Signed-off-by: Flavien Quesnel flavien.quesnel@citrix.com

@xen-git
Copy link

xen-git commented Aug 20, 2014

Can one of the admins verify this patch?

@coveralls
Copy link

Coverage Status

Coverage increased (+0.44%) when pulling 5a0977c8df4f0bc2601f188aa76791ec6e20c061 on fquesnel:unittestmaster into 66c89ea on xapi-project:master.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.47%) when pulling 72017f641f9a542a62bff0e1c6665f62fe5f8d50 on fquesnel:unittestmaster into 66c89ea on xapi-project:master.

Covering changes related to CA-142451.

Signed-off-by: Flavien Quesnel <flavien.quesnel@citrix.com>
@coveralls
Copy link

Coverage Status

Coverage increased (+0.47%) when pulling ab75df0 on fquesnel:unittestmaster into 66c89ea on xapi-project:master.

@matelakat
Copy link
Contributor

Looks good to me, OK to merge!

@germanop
Copy link
Contributor

I can merge but the situation has become a little bit confused.

This are the unit tests for #210. #210 has been merged and then ported in creedence with #213
along with #212.
Now, in creedence there is a backport of the fix plus the unit tests. The latter are not backports, though.
Would not it be easier (and surely less messy) to do everything in master first and then backport?
What are we going to do with this PR? Cherry-pick the code from Creedence and tag is
as "forwardported"?

@matelakat
Copy link
Contributor

@germanop Yes, I think we left with cherry-picking the xs64bit change to master. I agree that it is suboptimal. I can do the cherry picking to master, just let me know. So I guess let's close this PR, and just cherry-pick 2ddae13

The other thing we can do is to close this PR, and care about master branch later.

@germanop
Copy link
Contributor

Nooooo, do not close it!!!
Leave it open, we'll deal with it.

Please let's avoid creating too many PRs for the same reason

@matelakat
Copy link
Contributor

ok.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants