Skip to content

Improve error reporting when missing remote configurations #478

Improve error reporting when missing remote configurations

Improve error reporting when missing remote configurations #478

Triggered via pull request June 6, 2025 08:40
Status Failure
Total duration 8m 24s
Artifacts 4

build-pr.yml

on: pull_request
Build & Test on Ubuntu
6m 55s
Build & Test on Ubuntu
Build & Test on Windows
8m 16s
Build & Test on Windows
Fit to window
Zoom out
Zoom in

Annotations

45 errors
Build & Test on Ubuntu
Process completed with exit code 1.
Build & Test on Windows
Process completed with exit code 1.
config./remote gdb-async-off/program via --config-frozen= can not be overridden: config#L1
Port number not specified, cannot connect
multithread./remote gdb-async-off/sees all threads: multithread#L1
Port number not specified, cannot connect
config./remote gdb-async-off/program via --config= can be overridden: config#L1
Port number not specified, cannot connect
config./remote gdb-async-off/can specify program via --config-frozen=: config#L1
Port number not specified, cannot connect
config./remote gdb-async-off/program via --config-frozen= can not be overridden: config#L1
Port number not specified, cannot connect
config./remote gdb-async-off/config frozen forces specific launch type: config#L1
Port number not specified, cannot connect
config./remote/can specify program via --config=: config#L1
Port number not specified, cannot connect
config./remote/program via --config= can be overridden: config#L1
Port number not specified, cannot connect
config./remote/program via --config-frozen= can not be overridden: config#L1
Port number not specified, cannot connect
config./remote/can specify program via --config-frozen= using response file: config#L1
Port number not specified, cannot connect
config./remote/config frozen forces specific launch type: config#L1
Port number not specified, cannot connect
launch./remote/works with a space in file names: launch#L1
Port number not specified, cannot connect
launch remote./remote/can launch remote and hit a breakpoint: launch remote#L1
Port number not specified, cannot connect
multithread./remote/async resume for gdb-non-stop off: multithread#L1
Port number not specified, cannot connect
pause./remote/can be paused: pause#L1
Port number not specified, cannot connect
stop./remote/handles segv: stop#L1
Port number not specified, cannot connect
stop gdbserver./remote/do something: stop gdbserver#L1
Port number not specified, cannot connect
stop gdbserver."after each" hook for "/remote/do something": stop gdbserver#L1
no output event with category 'server' and output message 'gdbserver stopped' received after 12500 ms
terminated./remote/terminated event arrives on a short run: terminated#L1
Port number not specified, cannot connect
stop gdbserver./defaults/do something: stop gdbserver#L1
Port number not specified, cannot connect
stop gdbserver."after each" hook for "/defaults/do something": stop gdbserver#L1
no output event with category 'server' and output message 'gdbserver stopped' received after 12500 ms

Artifacts

Produced during runtime
Name Size Digest
test-logs-ubuntu Expired
2.98 MB
sha256:f4e3fcda924f5ab3443f4ba4692547d36574587527d144e7d552ba83d6ab0050
test-logs-windows Expired
1.48 MB
sha256:93104909c757bdfdfc88da77e3de8681c606d3ab957bfa97c3555f80197d4b1f
test-results-ubuntu Expired
28.9 KB
sha256:d06e6b86bf0bf138171f7872e7d5e5133b4adae96ce1f25a868b27f6d3d64aad
test-results-windows Expired
28 KB
sha256:f365a86a1eb60c0410779742ada6431a1e224022080bfdc90f4704baf879e6e1