-
Notifications
You must be signed in to change notification settings - Fork 206
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
Some error thrown at dsf gdb tests after that no other tests are executed. #1037
Comments
This is a new problem AFAICT, not sure what it is related to, but the logs that the build is generating are not being saved. So I need to add these extra logs to the build artifacts and see if I can get a clue as to what is happening. This may be related to the underlying issues preventing me from resolving #816 - the VMs + toolchains that GitHub actions runs on change regularly and the DSF GDB tests are more sensitive than most of the other tests in CDT. |
The problem is target platform is not resolving properly when running tests. See attached full log from last run of #1038: 1737048219553.log Key parts:
caused by:
|
When some types of failures happen, such as that in eclipse-cdt#1037, a log file is created, so save all .log files as artifacts. Part of eclipse-cdt#1037
On a recent update to the target platform, the DSF-GDB tests did not run because none of the changes matched the dsf filter. Going forward, include running DSF tests when any releng changes happen. This replaces commit 8d06425. That commit ran the tests all the time, which was too slow. Part of eclipse-cdt#1037
On a recent update to the target platform, the DSF-GDB tests did not run because none of the changes matched the dsf filter. Going forward, include running DSF tests when any releng changes happen. This replaces commit 8d06425. That commit ran the tests all the time, which was too slow. Part of eclipse-cdt#1037
On a recent update to the target platform, the DSF-GDB tests did not run because none of the changes matched the dsf filter. Going forward, include running DSF tests when any releng changes happen. This replaces commit 8d06425. That commit ran the tests all the time, which was too slow. Part of #1037
Some error thrown at dsf gdb tests after that no other tests are executed.
Originally posted by @raghucssit in #1035 (comment)
The text was updated successfully, but these errors were encountered: