On Sun, Sep 29, 2019 at 2:35 AM Gregory Farnum <gfarnum@xxxxxxxxxx> wrote: > On Sat, Sep 28, 2019 at 3:57 AM Jos Collin <jcollin@xxxxxxxxxx> wrote: >> >> >> >> On 28/09/19 1:48 PM, kefu chai wrote: >> > On Sat, Sep 28, 2019 at 3:22 PM Gregory Farnum <gfarnum@xxxxxxxxxx> wrote: >> >> >> >> Unfortunately you need full packages to work with teuthology, and in a default checkout that requires shaman. >> >> >> >> Many many years ago teuthology would work with local binaries, but that required the test machines match your build machine)s ABI and that’s not practical these days so I’m afraid you’re stuck with waiting on shaman. :( >> >> -Greg >> >> >> >> On Sat, Sep 28, 2019 at 12:05 AM Jos Collin <jcollin@xxxxxxxxxx> wrote: >> >>> >> >>> Hi Everyone, >> >>> >> >>> How can I make teuthology-suite command to fetch the code from my local >> >>> machine (laptop) and create a few jobs for me to test the code changes >> >>> in qa/tasks/? This would save a lot of time when I work on qa/tasks/, as >> >>> shaman would normally take 4-5 hrs to build. I tried changing >> >>> --suite-repo and --suite-branch, but it always points to shaman. >> > >> > probably you could post your command? i've been using "--suite-repo" >> > plus "--suite-branch", these options work just fine. >> >> As I was trying to reduce the wait time between my fixes, I tried >> different options. One of them was pushing to my git origin and it was >> pointing to shaman first and failing [1]. Now I logged out from >> teuthology and tried again and it starts working. But it seems getting >> the code from the master branch [2] and not from wip-yes-really-mean-it2. >> >> (venv) jcollin@teuthology:~/teuthology$ teuthology-suite -v >> --machine-type smithi --email jcollin@xxxxxxxxxx -p 50 --suite fs --ceph >> master --ceph-repo https://github.com/ceph/ceph.git --suite-branch >> wip-yes-really-mean-it2 --suite-repo >> https://github.com/joscollin/ceph.git --filter "volumes" > > Oh sorry I misread your initial email; suite-path and suite-repo should combine to let you fetch rest changes from your own GitHub just fine. > > For some reason pulpito isn’t loading for me right now so I can’t see that. My guess is that the package version failure is because the tip of master wasn’t built when you ran that command; you can try referencing another branch you know is stable and available or use the “newest” flag to deal with that. > i (partially) agree with Greg. the master branch of ceph is being updated constantly, and it takes around hours to build the packages, so there is a good chance that the master branch is still being built when you issue the command. that's why teuthology failed with the "Failed to fetch package version" message. instead of using another branch, i'd suggest specify a specific sha1. quote from the help message of teuthology-suite ==== 8< ==== -S <sha1>, --sha1 <sha1> The ceph sha1 to run against (overrides -c) If both -S and -c are supplied, -S wins, and there is no validation that sha1 is contained in branch ==== >8 ==== put in other words: teuthology-suite -v --machine-type smithi --email jcollin@xxxxxxxxxx -p 50 --suite fs --ceph-repo https://github.com/ceph/ceph.git --suite-branch wip-yes-really-mean-it2 --suite-repo https://github.com/joscollin/ceph.git --filter "volumes" --sha1 f28f35f79b896ea3f3183bf4066b6b0fdb9ffa31 --dry-run where "f28f35f79b896ea3f3183bf4066b6b0fdb9ffa31" is a random sha1 i found on shaman. see https://shaman.ceph.com/builds/ceph/master/f28f35f79b896ea3f3183bf4066b6b0fdb9ffa31/ . as all necessary builds have completed. >> >> [1] Failed to fetch package version from >> https://shaman.ceph.com/api/search/?status=ready&project=ceph&flavor=default&distros=centos%2F7%2Fx86_64&sha1=d516e54784e608a384d79c02debe9c0e481317a1 >> >> [2] >> http://pulpito.front.sepia.ceph.com/jcollin-2019-09-28_10:19:16-fs-master-distro-basic-smithi/ -- Regards Kefu Chai _______________________________________________ Dev mailing list -- dev@xxxxxxx To unsubscribe send an email to dev-leave@xxxxxxx
