Skip to content
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

[BUG] unit fails in unit tests (develop) #5496

Closed
dizzzz opened this issue Oct 11, 2024 · 1 comment · Fixed by #5497
Closed

[BUG] unit fails in unit tests (develop) #5496

dizzzz opened this issue Oct 11, 2024 · 1 comment · Fixed by #5497
Assignees
Labels
bug issue confirmed as bug regression

Comments

@dizzzz
Copy link
Member

dizzzz commented Oct 11, 2024

 19:17:53.032 [main] INFO org.exist.storage.BrokerPool -- shutdown complete !
[ERROR] Tests run: 341, Failures: 1, Errors: 0, Skipped: 2, Time elapsed: 3.512 s <<< FAILURE! -- in xquery.range.RangeTests

[ERROR] xqts.org.exist-db.xquery.range.test.optimizer.matches-field-filtered -- Time elapsed: 0.012 s <<< FAILURE!
org.junit.ComparisonFailure: 

expected:<[$result//stats:index[@type = 'new-range'][@optimization = 1] (assertXPath failed.)]> 

but was:<[&lt;stats:calls xmlns:stats="http://exist-db.org/xquery/profiling"&gt;
&lt;stats:function name="ot:matches-field-filtered" elapsed="0.002" calls="1" source="..../test/xquery/range/optimizer.xql [38:5]"/&gt;
&lt;stats:function name="range:matches" elapsed="0.002" calls="1" source="..../test/xquery/range/optimizer.xql [481:18]"/&gt;
&lt;stats:function name="collection" elapsed="0.0" calls="1" source=".../test/xquery/range/optimizer.xql [479:21]"/&gt;&lt;stats:index type="new-range" source="...range/src/test/xquery/range/optimizer.xql [481:18]" elapsed="0.002" calls="1" optimization-level="BASIC"/&gt;
&lt;/stats:calls&gt;]>

test fails due to change in optimization reporting, probably due to #4910

either

  • revert changes
  • repair tests

@adamretter

@dizzzz dizzzz added bug issue confirmed as bug regression labels Oct 11, 2024
@adamretter
Copy link
Member

I can try and fix this in the next day or two. It's strange we did not see this on the PR though

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug issue confirmed as bug regression
Projects
None yet
2 participants