microsoft / vscode-test

Testing utility for VS Code extensions
MIT License
242 stars 57 forks source link

dbus errors during VS Code installation #278

Closed zivshapiraintel closed 3 months ago

zivshapiraintel commented 3 months ago

Distributor ID: Ubuntu Description: Ubuntu 20.04.6 LTS Release: 20.04 Codename: focal

├── @vscode/test-cli@0.0.6 ├── @vscode/test-electron@2.3.10

Getting these errors during runTests execution. What causes them?

`Downloading VS Code 1.90.2 from https://update.code.visualstudio.com/1.90.2/linux-x64/stable Downloading VS Code (143925020B) Downloading VS Code [------------------------------] 0%Downloading VS Code [------------------------------] 0%Downloading VS Code [------------------------------] 0%Downloading VS Code [------------------------------] 1%Downloading VS Code [------------------------------] 1%Downloading VS Code [------------------------------]

...

[=============================-] 100%Downloading VS Code [=============================-] 100%Downloading VS Code [=============================-] 100%Downloaded VS Code into /data/workspace/XXXXXXXX/extensions/vscode/.vscode-test/vscode-linux-x64-1.90.2 Downloaded VS Code into /data/workspace/XXXXXXXXX/extensions/vscode/.vscode-test/vscode-linux-x64-1.90.2 Downloading VS Code [==============================] 100%[4831:0623/230859.727074:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory [4831:0623/230901.665173:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory [4831:0623/230901.665222:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory [4831:0623/230901.667020:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix") [4831:0623/230901.667161:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix") [4831:0623/230901.667207:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix") [4831:0623/230901.667250:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix") [4831:0623/230901.940150:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory [4831:0623/230901.940203:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory [4831:0623/230901.940228:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory [main 2024-06-24T03:09:02.112Z] update#setState disabled [main 2024-06-24T03:09:02.113Z] update#ctor - updates are disabled by the environment [4831:0623/230902.115171:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix") [4855:0623/230902.378894:ERROR:viz_main_impl.cc(196)] Exiting GPU process due to errors during initialization [4878:0623/230902.493068:ERROR:command_buffer_proxy_impl.cc(131)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer. workbench#open() [4831:0623/230904.215817:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix") Started local extension host with pid 4952. IExtensionHostStarter.start() took 37 ms. `

connor4312 commented 3 months ago

I believe these come from Electron and are generally not something you need to worry about (look like you're running with verbose logging.) dbus is used for all sorts of things to interact with the Linux host, but VS Code should handle a lack of dbus just fine. Are you running into problems?

zivshapiraintel commented 3 months ago

I believe these come from Electron and are generally not something you need to worry about (look like you're running with verbose logging.) dbus is used for all sorts of things to interact with the Linux host, but VS Code should handle a lack of dbus just fine. Are you running into problems?

Thanks @connor4312 I have no screenshots for my vs code extension tests, so I don't know if there are issues. I thought this was an issue, since these are errors. IF there is some way to disable the GPU and also add a valid address, maybe that will make the errors stop.

But thanks for the tip on simply ignoring this.

connor4312 commented 3 months ago

You can pass electron/chromium flags like --disable-gpu, but I don't know if all behaviors that are causing those logging are able to be disabled.