Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide a quiet mode where nothing but the total startup time is displayed #33

Closed
yphus opened this issue Mar 30, 2021 · 3 comments · Fixed by #37
Closed

Provide a quiet mode where nothing but the total startup time is displayed #33

yphus opened this issue Mar 30, 2021 · 3 comments · Fixed by #37
Assignees

Comments

@yphus
Copy link

yphus commented Mar 30, 2021

Using both --cmd-stderr=/dev/null --cmd-stdout=/dev/null already helps but that's not enough as etrace itself can print msg on stderr. It would be great to have a way to only output the total startup time.

$ etrace exec -s -d -t --cmd-stderr=/dev/null --cmd-stdout=/dev/null vlc -n 5 
Total startup time: 2.552092291s
2021/03/30 17:08:18 xdotool.go:91: X Error of failed request:  BadValue (integer parameter out of range for operation)
  Major opcode of failed request:  113 (X_KillClient)
  Value in failed request:  0x440000a
  Serial number of failed request:  18
  Current serial number in output stream:  20

2021/03/30 17:08:18 main.go:120: 
Total startup time: 2.548430002s
2021/03/30 17:08:20 xdotool.go:91: X Error of failed request:  BadValue (integer parameter out of range for operation)
  Major opcode of failed request:  113 (X_KillClient)
  Value in failed request:  0x440000a
  Serial number of failed request:  18
  Current serial number in output stream:  20

2021/03/30 17:08:20 main.go:120: 
Total startup time: 2.554694062s

@anonymouse64 anonymouse64 self-assigned this Mar 30, 2021
@anonymouse64
Copy link
Contributor

I can't reproduce the situation in which xdotool fails, but I see the code where a message is printed off, so I can remove that, but can you clarify what system you are running on to reproduce this error? I am using stock Groovy 20.10 desktop with proprietary nvidia drivers and X11.

anonymouse64 added a commit that referenced this issue Apr 2, 2021
This provides a better user experience, by returning full error messages with
full details including the output of xdotool, such that the caller can decide
whether to log the error or ignore it.

Fixes: #33

Signed-off-by: Ian Johnson <ian.johnson@canonical.com>
anonymouse64 added a commit that referenced this issue Apr 2, 2021
This provides a better user experience, by returning full error messages with
full details including the output of xdotool, such that the caller can decide
whether to log the error or ignore it.

Fixes: #33

Signed-off-by: Ian Johnson <ian.johnson@canonical.com>
anonymouse64 added a commit that referenced this issue Apr 2, 2021
This provides a better user experience, by returning full error messages with
full details including the output of xdotool, such that the caller can decide
whether to log the error or ignore it.

Fixes: #33

Signed-off-by: Ian Johnson <ian.johnson@canonical.com>
@anonymouse64
Copy link
Contributor

So this should be fixed on edge in a while, but I'm still curious if you have a better reproducer for how these messages show up for you

@yphus
Copy link
Author

yphus commented Apr 6, 2021

I was able to reproduce it with a Focal desktop on Intel/X11. Tested --edge it works like a charm. thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants