-
Notifications
You must be signed in to change notification settings - Fork 52
Log debug info for #1897 #1975
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
Log debug info for #1897 #1975
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1975 +/- ##
============================================
+ Coverage 65.27% 65.39% +0.12%
- Complexity 1804 1817 +13
============================================
Files 320 320
Lines 12382 12428 +46
Branches 1110 1118 +8
============================================
+ Hits 8082 8127 +45
- Misses 3891 3892 +1
Partials 409 409
Continue to review full report at Codecov.
|
|
Ah, okay, the log was quite a bit more above the assertion failure message: There certainly exists one tree item, but its text is empty. Maybe a race condition: we wait until there becomes one tree item, but we check its text too early before the UI thread sets a proper text. |
|
There may have been an execution error with launching devappserver. As part of trying to diagnose the very strange test problems I encountered in #1529, I had added some support to the tests to dump the console output from launching the devappserver. (I never did get to the bottom of #1529) |
|
@briandealwis That's very interesting. Before that, what seems weird though is that the test calls |
As might happen if the launched JVM never actually ran for some reason… |
|
I wonder if |
For #1897.
SWTBotTreeItem.toString()will do the job.