-
Notifications
You must be signed in to change notification settings - Fork 470
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
Core18 (Washington Post) regression failure #658
Comments
Previous index:
Current index:
|
I reverted the commit (c4ab6bf) and removed the
How do we want to handle this case? Should we add the
and the regressions change to:
Some increase, some decrease - never by much. Couple of options:
|
The first option and removing the Regarding the empty docs...I think some of them are actually somewhat empty in content, such as:
If we want to have minimal empty docs by adding to content, perhaps we can try |
I think @r-clancy 's fix lg - the AP/P30 differences are noise, I think...
Let's try this and see and see what we get in terms of regression numbers? |
* add tct_colbert-v2 integration test * add distilbert_tasb integration test Co-authored-by: Lin Jack <[email protected]> Co-authored-by: justram <[email protected]>
@emmileaf reported a regression failure in #654 but exposing here at top level so this doesn't get buried.
@emmileaf can you copy and paste the regression log in this issue?
The text was updated successfully, but these errors were encountered: