jenkins-bot has submitted this change and it was merged.

Change subject: Disable recalcitrant relevancy test
......................................................................


Disable recalcitrant relevancy test

I'm giving up, I'll try to spend more time later on this to understand
what's happening here.
This test is not made to assert that critical features in the are properly
working but more to assert that results are ordered by field importance
title>redirect>category ...
This is imo not as simple and this test forget all the other factors
that affect scoring (norms, maxDoc, avgFieldLength..)

Change-Id: Ifdc62aa3c71c894a5689476091ed4f29ea2b7439
---
M tests/browser/features/relevancy_api.feature
1 file changed, 10 insertions(+), 0 deletions(-)

Approvals:
  Cindy-the-browser-test-bot: Looks good to me, but someone else must approve
  EBernhardson: Looks good to me, approved
  jenkins-bot: Verified



diff --git a/tests/browser/features/relevancy_api.feature 
b/tests/browser/features/relevancy_api.feature
index bfd8a1b..6cf42bd 100644
--- a/tests/browser/features/relevancy_api.feature
+++ b/tests/browser/features/relevancy_api.feature
@@ -36,6 +36,16 @@
     # 2. Its quite possible for the second result to be deeper in the result 
list for a few seconds after the pages are
     # created. It gets its position updated by the link counting job which has 
to wait for refreshing and undelaying.
 
+  # FIXME: find proper settings to make this test pass consistently.
+  # The causes are still unclear and mostly related to shard distribution
+  # and DFS problems. Unfortunately it's extremely hard to debug because
+  # the global context built by DFS is not applied when running in explain
+  # mode.
+  # Possible cause can be:
+  # - a bug in DFS
+  # - number of documents, field size or term freq that can vary from time to
+  #   time possibly because we generate random docs?
+  @expect_failure
   Scenario: Results are sorted based on what part of the page matches: title, 
redirect, category, etc
     When I api search with query independent profile classic_noboostlinks for 
Relevancytest
     Then Relevancytest is the first api search result

-- 
To view, visit https://gerrit.wikimedia.org/r/305636
To unsubscribe, visit https://gerrit.wikimedia.org/r/settings

Gerrit-MessageType: merged
Gerrit-Change-Id: Ifdc62aa3c71c894a5689476091ed4f29ea2b7439
Gerrit-PatchSet: 2
Gerrit-Project: mediawiki/extensions/CirrusSearch
Gerrit-Branch: master
Gerrit-Owner: DCausse <dcau...@wikimedia.org>
Gerrit-Reviewer: Cindy-the-browser-test-bot <bernhardsone...@gmail.com>
Gerrit-Reviewer: EBernhardson <ebernhard...@wikimedia.org>
Gerrit-Reviewer: Gehel <gleder...@wikimedia.org>
Gerrit-Reviewer: Manybubbles <never...@wikimedia.org>
Gerrit-Reviewer: Smalyshev <smalys...@wikimedia.org>
Gerrit-Reviewer: jenkins-bot <>

_______________________________________________
MediaWiki-commits mailing list
MediaWiki-commits@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-commits

Reply via email to