Description of problem: I've tried to run /CoreOS/fuse using new beaker but failed, which can pass in rhts. How reproducible: always Steps to Reproduce: 1. kernel_workflow.py -S rhts.redhat.com -u yanwang -d RHEL6.0-Snapshot-5 -P kernel -t /CoreOS/fuse -w "FUSE Sanity Testing for RHEL6." >xxx.xml 2. bkr job-submit --convert xxx.xml Actual results: there are " {"event": ["Event", "end", "5619b3e6-6e15-11df-9c51-00e081467136", {}, null, {"task_id": "48c32ace-6e15-11df-8f0f-00e081467136", "rc": 1}]}" shown in the web-ui. the failed log shown: Try to run 'mount -t fuse ./sshfs-fuse-2.2/sshfs#localhost:/root './MP1''... /bin/sh: ./sshfs-fuse-2.2/sshfs: Permission denied Failed! this is failed job link: https://beaker.engineering.redhat.com/jobs/1506 I select part of these testcase to re-run in beaker,pls refer to these below links: https://beaker.engineering.redhat.com/jobs/1699, fail again and these testcases can pass in rhts: http://rhts.redhat.com/cgi-bin/rhts/jobs.cgi?id=161106 Expected results: tese case can run Additional info:
Marian, It looks like a yum issue to me. The metadata gets out of sync and it suggests running yum metadata clean all. Can we update the harness to do that?
Thanks Bill, I will try it out. Q: How often is the repo rebuilt? IIUC it does not happen instantly after adding/changing test as I had issues where I updated a test (w/o changing metadata) while job was running and it failed due to checksum mismatch. Workaround: In the meantime, simple rerunning the tests should be OK.
The repo is rebuilt everytime someone uploads a new task.
Fixed upstream.
ping - can this be closed?
The yum part is fixed now but the test is still failing. I noticed some of the tests are passing all right (especially some i386 and s390x), and there were also some tests failing on RHTS as well. Yanfu, are these (RHTS vs. Beaker) really equivalent tests?
(In reply to comment #6) > The yum part is fixed now but the test is still failing. > > I noticed some of the tests are passing all right (especially some i386 and > s390x), and there were also some tests failing on RHTS as well. > > Yanfu, are these (RHTS vs. Beaker) really equivalent tests? yes, I check the fuse testsuite in rhts and beaker, they are both use rh-tests-fuse-1.1-17.noarch. now I'm re-testing again,let's check again when these jobs finish: i386 arch: http://rhts.redhat.com/cgi-bin/rhts/jobs.cgi?id=165424 beaker job: 6325 x86_64: http://rhts.redhat.com/cgi-bin/rhts/jobs.cgi?id=165425 beaker job: 6326
seems fuse test can done in beaker now by check these above jobs, except virt part which may separated for the problem.
please open a separate bug for the virt issue if its a real issue. Thanks