Dne Čt 24. listopadu 2011 10:43:41, Lukas Ocilka napsal(a):
On 11/23/2011 10:06 PM, Alexander Graf wrote:
When running the stdout and stderr test cases while building yast2-core for ARM, we execute processes slower than the yast developer machines apparently :).
The test cases expect data to flow between the ycp code and cat within 50 ms, but we can't guarantee that. In fact, it basically never worked in my tests.
The real fix would probably to listen on the socket and see if new data comes in and only then read from there, but I'm not sure it's worth it for a test case. Instead, we can just increase the sleeps to something really high so we definitely catch all the shiny new data on the other end of the pipe.
What about rather checking for architecture and raise the sleep time only in case of ARM detected (if possible)? I'd prefer not changing it for the rest of architectures.
Even the .probe-agent in YaST knows the arm architecture. But I'm not sure if we can avoid faking the architecture and use the real architecture in the testsuite. Jiri -- Regards, Jiri Srain Project Manager --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: jsrain@suse.cz Lihovarska 1060/12 tel: +420 284 084 659 190 00 Praha 9 fax: +420 284 084 001 Czech Republic http://www.suse.cz -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org