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(a)redhat.com> wrote:

It depends which code you mean. There is nothing in common between ’suite-repo’ and ’suite-branch’, they are not used for building rpm. The code of ceph components which are buildable is one thing, the code of tests is another thing. If you are just modifying qa/tasks it is more likely related to the code of tests which is not required to build rebuilt on shaman to be delivered to test environment. And thus you can use --sha1 option for pointing the ceph builds and --suite-repo and --suite-branch to the tip of your branch. There is another option "--suite-relpath" which allows you to take a definition of the test from you local machine, but it does take to the code of tests to the teuthology worker. So your only choice is to push changes to github but still continue to use sha1 of previous builds.

On 28/09/19 1:48 PM, kefu chai wrote: 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(a)redhat.com -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" [1] Failed to fetch package version from https://shaman.ceph.com/api/search/?status=ready&project=ceph&flavo… [2] http://pulpito.front.sepia.ceph.com/jcollin-2019-09-28_10:19:16-fs-master-d…

On Sun, Sep 29, 2019 at 2:35 AM Gregory Farnum &lt;gfarnum(a)redhat.com&gt; wrote: 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(a)redhat.com -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/f28f35f79b896ea3f3183bf4066b6b0f… . as all necessary builds have completed. -- Regards Kefu Chai