Bug 15426

Summary:	dbus-wait timeout uses a 'success' exit code
Product:	[Yocto Project Subprojects] Sato	Reporter:	Richard Purdie <richard.purdie>
Component:	sato	Assignee:	Ross Burton <ross.burton>
Status:	NEW ---	QA Contact:
Severity:	normal
Priority:	Medium	CC:	dixitparmar19, randy.macleod, ross.burton
Version:	svn
Target Milestone:	6.1
Hardware:	x86
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	No (bug/feature does not impact docs)

Description Richard Purdie 2024-03-07 12:19:40 UTC

dbus-wait uses a "success" exit code for timeout:

https://git.yoctoproject.org/dbus-wait/tree/dbus-wait.c#n33

This should probably be configurable so the caller can decide whether that should be an error or not. This was making usage in runtime desktop image testing more challenging than it should be.

The timeout should also perhaps be an optional parameter?

Comment 1 Dixit Parmar 2024-10-21 06:14:39 UTC

Hi,
Can we use dbus_connection_read_write_dispatch's timeout arg option, which can be based on a command-line parameter passed to the application, instead of the fixed wait time of 60 seconds?

Comment 2 Dixit Parmar 2024-10-21 06:33:32 UTC

(In reply to Dixit Parmar from comment #1)
> Hi,
> Can we use dbus_connection_read_write_dispatch's timeout arg option, which
> can be based on a command-line parameter passed to the application, instead
> of the fixed wait time of 60 seconds?

No, because it can not be specific to a match rule or connection type. :)