Project

General

Profile

Actions

Bug #3760

closed

Falacious test error in TestQuickSearchService

Added by François ARMAND over 9 years ago. Updated almost 8 years ago.

Status:
Released
Priority:
3
Category:
Architecture - Refactoring
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Regression:

Description

Sometime, when executing test on Rudder, we are seing that test error:

11:25:22 Running com.normation.rudder.services.nodes.TestQuickSearchService
11:30:22 Tests run: 5, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 300.287 sec <<< FAILURE!
...
11:30:25 Failed tests: test1: the search for \'node\' in id should::not matchsuperfluous server entries(com.normation.rudder.services.nodes.TestQuickSearchService): Error in quick search query

It's really hard to reproduce, and so does look like a race condition / thread deadlock happening sometimes. On one occasion, I was able to see that the test (inmemory) LDAP server when stalling and connexion where not responding anymore. Has the same LDAP server is used for each test, the following test was in error.

So, the idea would be to start a fresh new LDAP server for each test to see if it makes the error disapear.

Actions #1

Updated by François ARMAND over 9 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from François ARMAND to Nicolas CHARLES
  • Pull Request set to https://github.com/Normation/rudder/pull/271
Actions #2

Updated by François ARMAND over 9 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100
Actions #4

Updated by Nicolas PERRON over 9 years ago

  • Status changed from Pending release to Released
Actions #5

Updated by Nicolas PERRON over 9 years ago

This bug has been fixed in Rudder 2.4.7, which was released today.
Check out:

Actions #6

Updated by Benoît PECCATTE almost 8 years ago

  • Category changed from 40 to Architecture - Refactoring
Actions

Also available in: Atom PDF