|
Hi all, I have discussed with Daniel about the running time for each cases before and we set the standard as 10M, if one can’t finish after running 10M we will see it as Timeout
and report bug on FDO(such as : Bug 77474 - [PNV/IVB/HSW]igt/gem_tiled_swapping is slow and
Bug 77475 - [PNV/IVB/HSW]igt//kms_pipe_crc_basic/read-crc-pipe-A is slow) Now the true status is that i-g-t have more than 650+ subcases, running a whole round of testing will cost such a long time on QA side(beside that Timeout cases),
QA also need to spend more time to analysis the result changing on each platforms. You can find an example with this page:
http://tinderbox.sh.intel.com/PRTS_UI/prtsresult.php?task_id=2778 for how long one testing round cost. With the table of subtask:10831 on the page which for i-g-t test cases on BDW. Testing start at 19:16 PM and finished at 03:25 AM the next day, cost about
8 hours to run 638 test cases. Each cases finished less than 10M as we expect, but the full time it too large, especially the BDW is the powerful machine on our side, ILK or PNV may take more than
10 hours. We not only run i-g-t but also need to test the piglit/performance/media which already need time. Do we have any solutions to reduce the running time for whole i-g-t? it’s a pressing problem for QA after seeing the i-g-t case count enhance from 50 ->600+. Best Regards~~ Open Source Technology Center (OTC) Terence Yang（杨光） Tel:
86-021-61167360 iNet:
8821-7360 |
_______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/intel-gfx
