Hi guys, Chris forgot to copy this to the autotest mailing list, and I
feel it's important, specially for those of you who still didn't follow
up with the latest developments, mainly:
The autotest tests were split to their own repos,
The virt test has its own, separate repo,
There's a new mailing list for development of the virt tests, so anybody
who cares about it should subscribe to that mailing list, since we'll
stop copying autotest to these messages.
Cheers,
Lucas
-------- Original Message --------
Subject: [Virt-test-devel] The autotest dust has settled
Date: Tue, 02 Oct 2012 11:42:44 -0400
From: Chris Evich <[email protected]>
To: tangchen <[email protected]>, Yu Mingfei
<[email protected]>, Satheesh Rajendran
<[email protected]>, Prem Karat
<[email protected]>, [email protected],
[email protected], liyang <[email protected]>
CC: Martin Jenner <[email protected]>, [email protected]
Hey guys,
I think the major disruptions have stopped for now, and it's safe to
begin migrating old code. Also, don't forget to subscribe to new
virt-test mailing list:
http://www.redhat.com/mailman/listinfo/virt-test-devel
I'm planning to fix the libvirt tracking issue problem in the next few
weeks. My plan is to manually move (i.e. copy/paste) all our stuff over
to virt-test repo. Unless anyone has a better idea.
I'm not sure where you're at in terms of the new client/tests repo and
submodules. I found them quite confusing at first, but here's a good
article on how the submodule stuff works:
http://git-scm.com/book/en/Git-Tools-Submodules
As the article warns, it can be confusing when after a 'git submodule
update' client/tests is left in detached-head state. I also ran into a
ton of problems trying to rebase my local branches/changes across the
repos (i.e. from old client/tests/... into new client/tests/...).
I ended up taking a more brute-force approach:
+ Copy all the files important to me from my local branches into
/tmp.
+ Go to github and fork https://github.com/autotest/virt-test
(button in upper right)
+ Checkout next and reset to latest upstream
+ Checkout master and reset to latest upstream
+ Push to origin master (i.e. to my autotest github fork)
+ Use 'git submodule init' from top-level 'autotest' directory.
+ Go into autotest/client/tests
+ Checkout next (of the submodule)
+ Checkout master (of the submodule)
+ Fix 'origin' to point at my fork:
git remote set-url origin [email protected]:<username>/virt-test.git
+ Add back in the 'upstream' remote:
git remote add upstream git://github.com/autotest/virt-test.git
+ Force push to origin (i.e. to my virt-test github fork)
+ one-by-one recreate changes from files I copied into /tmp into
new local branches of virt-test repo.
+ Pushing to my virt-test github fork as needed
Going-forward, just treat 'autotest/' and 'autotest/client/tests' as
separate but 'nested' repositories. This probably means keeping
autotest on 'next' branch, and remembering to checkout the right branch
of client/tests as you work.
-----
I'm sensitive to the disruptions these changes probably caused,
hopefully we can quickly put them behind us. I believe it will be
beneficial to have the new mailing-list and repo. dedicated to
virt-tests. As always, please feel free to contact me directly for help
if you need it. Thanks.
--
Chris Evich, RHCA, RHCE, RHCDS, RHCSS
Quality Assurance Engineer
e-mail: cevich + `@' + redhat.com o: 1-888-RED-HAT1 x44214
_______________________________________________
Virt-test-devel mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/virt-test-devel
_______________________________________________
Autotest-kernel mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/autotest-kernel
