-
Notifications
You must be signed in to change notification settings - Fork 155
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
Failure of test: CompletionTest.testCompletionService() #906
Labels
test
junit test related things
Comments
This was referenced Jul 3, 2023
This issue might have been solved by PR 725 in SWT. |
HeikoKlare
added a commit
to HeikoKlare/eclipse.platform.ui
that referenced
this issue
Jul 25, 2023
…pse-platform#907 In the CompletionTest, the check for the completion proposals waits for the full list of proposal items to be calculated. The condition is never fulfilled because it checks for the first proposal item to change while only its data will be replaced. In consequence, waiting for the condition always runs into a timeout. This change corrects the conditions and refactors the logic for checking for the "computing" entry into a separate method. Contributes to eclipse-platform#906 and eclipse-platform#907
HeikoKlare
added a commit
to HeikoKlare/eclipse.platform.ui
that referenced
this issue
Jul 25, 2023
…pse-platform#907 In the CompletionTest, the check for the completion proposals waits for the full list of proposal items to be calculated. The condition is never fulfilled because it checks for the first proposal item to change while only its data will be replaced. In consequence, waiting for the condition always runs into a timeout. This change corrects the conditions and refactors the logic for checking for the "computing" entry into a separate method. Contributes to eclipse-platform#906 and eclipse-platform#907
HeikoKlare
added a commit
to HeikoKlare/eclipse.platform.ui
that referenced
this issue
Jul 25, 2023
…pse-platform#907 In the CompletionTest, the check for the completion proposals waits for the full list of proposal items to be calculated. The condition is never fulfilled because it checks for the first proposal item to change while only its data will be replaced. In consequence, waiting for the condition always runs into a timeout. This change corrects the conditions and refactors the logic for checking for the "computing" entry into a separate method. Contributes to eclipse-platform#906 and eclipse-platform#907
HeikoKlare
added a commit
to HeikoKlare/eclipse.platform.ui
that referenced
this issue
Jul 25, 2023
…atform#906 The test cases for completion proposals in CompletionTest depend on specific timing behavior of a test proposal processor. On one hand, this is prone to errors if proper timing is not given on the test environment. On the other hand, the tests run unnecessarily long because of waiting long enough. This change replaces the fixed-time waiting of the LongRunningBarContentAssistProcessor with an explicit trigger that finalizes the content calculation as soon as some barrier is reached within the tests.
HeikoKlare
added a commit
to HeikoKlare/eclipse.platform.ui
that referenced
this issue
Jul 25, 2023
…atform#906 eclipse-platform#907 The test cases for completion proposals in CompletionTest depend on specific timing behavior of a test proposal processor. On one hand, this is prone to errors if proper timing is not given on the test environment. On the other hand, the tests run unnecessarily long because of waiting long enough. This change replaces the fixed-time waiting of the LongRunningBarContentAssistProcessor with an explicit trigger that finalizes the content calculation as soon as some barrier is reached within the tests. Contributes to eclipse-platform#906 and eclipse-platform#907
HeikoKlare
added a commit
to HeikoKlare/eclipse.platform.ui
that referenced
this issue
Jul 25, 2023
…atform#906 eclipse-platform#907 The test cases for completion proposals in CompletionTest depend on specific timing behavior of a test proposal processor. On one hand, this is prone to errors if proper timing is not given on the test environment. On the other hand, the tests run unnecessarily long because of waiting long enough. This change replaces the fixed-time waiting of the LongRunningBarContentAssistProcessor with an explicit trigger that finalizes the content calculation as soon as some barrier is reached within the tests. Contributes to eclipse-platform#906 and eclipse-platform#907
HeikoKlare
added a commit
that referenced
this issue
Jul 25, 2023
In the CompletionTest, the check for the completion proposals waits for the full list of proposal items to be calculated. The condition is never fulfilled because it checks for the first proposal item to change while only its data will be replaced. In consequence, waiting for the condition always runs into a timeout. This change corrects the conditions and refactors the logic for checking for the "computing" entry into a separate method. Contributes to #906 and #907
HeikoKlare
added a commit
to HeikoKlare/eclipse.platform.ui
that referenced
this issue
Jul 25, 2023
…atform#906 eclipse-platform#907 The test cases for completion proposals in CompletionTest depend on specific timing behavior of a test proposal processor. On one hand, this is prone to errors if proper timing is not given on the test environment. On the other hand, the tests run unnecessarily long because of waiting long enough. This change replaces the fixed-time waiting of the LongRunningBarContentAssistProcessor with an explicit trigger that finalizes the content calculation as soon as some barrier is reached within the tests. Contributes to eclipse-platform#906 and eclipse-platform#907
HeikoKlare
added a commit
to HeikoKlare/eclipse.platform.ui
that referenced
this issue
Jul 26, 2023
Provide more meaningful error message in case any of the test cases in CompletionTest fails. Particularly also explicitly validate whether the proposal list widget has been disposed concurrently. Remove typo in method name. Contributes to eclipse-platform#906
HeikoKlare
added a commit
to HeikoKlare/eclipse.platform.ui
that referenced
this issue
Jul 26, 2023
Provide more meaningful error message in case any of the test cases in CompletionTest fails. Particularly also explicitly validate whether the proposal list widget has been disposed concurrently. Remove typo in method name. Contributes to eclipse-platform#906
HeikoKlare
added a commit
to HeikoKlare/eclipse.platform.ui
that referenced
this issue
Jul 26, 2023
Provide more meaningful error message in case any of the test cases in CompletionTest fails. Particularly also explicitly validate whether the proposal list widget has been disposed concurrently. Remove typo in method name. Contributes to eclipse-platform#906
HeikoKlare
added a commit
to HeikoKlare/eclipse.platform.ui
that referenced
this issue
Jul 26, 2023
Provide more meaningful error message in case any of the test cases in CompletionTest fails. Particularly also explicitly validate whether the proposal list widget has been disposed concurrently. Contributes to eclipse-platform#906
HeikoKlare
added a commit
that referenced
this issue
Jul 26, 2023
Provide more meaningful error message in case any of the test cases in CompletionTest fails. Particularly also explicitly validate whether the proposal list widget has been disposed concurrently. Contributes to #906
HeikoKlare
added a commit
to HeikoKlare/eclipse.platform.ui
that referenced
this issue
Jul 26, 2023
…atform#906 eclipse-platform#907 The test cases for completion proposals in CompletionTest depend on specific timing behavior of a test proposal processor. On one hand, this is prone to errors if proper timing is not given on the test environment. On the other hand, the tests run unnecessarily long because of waiting long enough. This change replaces the fixed-time waiting of the LongRunningBarContentAssistProcessor with an explicit trigger that finalizes the content calculation as soon as some barrier is reached within the tests. Contributes to eclipse-platform#906 and eclipse-platform#907
HeikoKlare
added a commit
to HeikoKlare/eclipse.platform.ui
that referenced
this issue
Jul 27, 2023
…atform#906 The test cases for completion proposals in CompletionTest depend on specific timing behavior of a test proposal processor. On one hand, this is prone to errors if proper timing is not given on the test environment. On the other hand, the tests run unnecessarily long because of waiting long enough. This change replaces the fixed-time waiting of the LongRunningBarContentAssistProcessor with an explicit trigger that finalizes the content calculation as soon as some barrier is reached within the tests. In addition, the long-running processor is only enabled on demand and will be finalized whenever a test case was executed to avoid that the processor thread is leaking to the next test case. Contributes to eclipse-platform#906
HeikoKlare
added a commit
to HeikoKlare/eclipse.platform.ui
that referenced
this issue
Jul 31, 2023
…atform#906 The test cases for completion proposals in CompletionTest depend on specific timing behavior of a test proposal processor. On one hand, this is prone to errors if proper timing is not given on the test environment. On the other hand, the tests run unnecessarily long because of waiting long enough. This change replaces the fixed-time waiting of the LongRunningBarContentAssistProcessor with an explicit trigger that finalizes the content calculation as soon as some barrier is reached within the tests. In addition, the long-running processor is only enabled on demand and will be finalized whenever a test case was executed to avoid that the processor thread is leaking to the next test case. Contributes to eclipse-platform#906
Fails also in #939 |
praveen-skp
pushed a commit
to praveen-skp/eclipse.platform.ui
that referenced
this issue
Aug 8, 2023
…pse-platform#907 In the CompletionTest, the check for the completion proposals waits for the full list of proposal items to be calculated. The condition is never fulfilled because it checks for the first proposal item to change while only its data will be replaced. In consequence, waiting for the condition always runs into a timeout. This change corrects the conditions and refactors the logic for checking for the "computing" entry into a separate method. Contributes to eclipse-platform#906 and eclipse-platform#907
praveen-skp
pushed a commit
to praveen-skp/eclipse.platform.ui
that referenced
this issue
Aug 8, 2023
Provide more meaningful error message in case any of the test cases in CompletionTest fails. Particularly also explicitly validate whether the proposal list widget has been disposed concurrently. Contributes to eclipse-platform#906
It is failing in jenkins on almost every build. I'm going to disable the test.
|
iloveeclipse
added a commit
to iloveeclipse/eclipse.platform.ui
that referenced
this issue
Aug 16, 2023
iloveeclipse
added a commit
to iloveeclipse/eclipse.platform.ui
that referenced
this issue
Aug 16, 2023
iloveeclipse
added a commit
to iloveeclipse/eclipse.platform.ui
that referenced
this issue
Aug 16, 2023
iloveeclipse
added a commit
that referenced
this issue
Aug 16, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The test
CompletionTest.testCompletionService()
failed for Mac OS in this run of the PR #755 :The text was updated successfully, but these errors were encountered: