Bug 14769

Summary:	time out waiting for qemu to start
Product:	[QA/Testing] Functional (self) Testing	Reporter:	Jon Mason <jon.mason>
Component:	oe-selftest	Assignee:	Unassigned <unassigned>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	normal
Priority:	Medium	CC:	alexandre.belloni, randy.macleod, richard.purdie
Version:	4.0
Target Milestone:	4.1
Hardware:	x86
OS:	Multiple
Whiteboard:	AB-INT AB-NON-SSD
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	Don't know

Description Jon Mason 2022-03-24 21:09:03 UTC

In https://autobuilder.yoctoproject.org/typhoon/#/builders/79/builds/3325/steps/15/logs/stdio
there are multiple instances of:

waiting at most 300 seconds for qemu pid (03/22/22 02:37:28)
Qemu pid didn't appear in 300 seconds (03/22/22 02:42:29)

Each of which corresponds to the systemtap test instance failing.

Comment 1 Alexandre Belloni 2022-03-24 21:29:28 UTC

This was centos7-ty-4

Comment 2 Richard Purdie 2022-04-16 10:21:46 UTC

Copy done in 296.2610318660736 seconds
Copy done in 293.46104764938354 seconds

So both were really slow at copying and then qemu didn't boot in 4s. Likely and IO load issue.

Comment 3 Richard Purdie 2022-04-16 10:22:40 UTC

Mark as duplicate of copying too long bug

*** This bug has been marked as a duplicate of bug 14486 ***