I don't see the test, so hard for me to tell for sure... but there are lots of scaffolding around this class as I inserted an empty test containing an assumption and it initializes lots of stuff; the assumption has to be triggering there somewhere.
Once your test fails or assume-fails, locate: TEST-org.apache.solr.client.solrj.io.stream.StreamExpressionTest.xml and see inside; there should be a stack trace leading to the failed assumption. Dawid On Tue, Feb 21, 2017 at 9:00 PM, Joel Bernstein <joels...@gmail.com> wrote: > I traced the issue to a specific change that was made to the > StreamExpressionTest. I'm figuring out the best way to address the issue. > > Joel Bernstein > http://joelsolr.blogspot.com/ > > On Tue, Feb 21, 2017 at 2:52 PM, Joel Bernstein <joels...@gmail.com> wrote: >> >> Hi Dawid, >> >> It does appear to be related to an assumption. I researching what the >> issue is. Also I was using -Dtestmethod to specify the method which does not >> seem to be correct. I have a reproduce method that looks like this: >> >> NOTE: reproduce with: ant test -Dtestcase=StreamExpressionTest >> -Dtests.method=testSignificantTermsStream -Dtests.seed=144DBB9558834AFE >> -Dtests.slow=true -Dtests.locale=ro -Dtests.timezone=Africa/Johannesburg >> -Dtests.asserts=true -Dtests.file.encoding=UTF-8 >> >> >> Using -Dtests.method still gives me problems with the assumption. I'm >> starting to think that the StreamExpressionTest testcase isn't structured >> properly to run individual methods. But this would be a recent issue. >> >> >> Joel Bernstein >> http://joelsolr.blogspot.com/ >> >> On Tue, Feb 21, 2017 at 2:36 PM, Dawid Weiss <dawid.we...@gmail.com> >> wrote: >>> >>> Joel, >>> >>> your test is being executed, but there is some kind of assumption that >>> is thrown within the body of the method (or in setup/ teardown) that >>> is causing the test to be ignored. Assumptions are regular exceptions >>> -- try wrapping in try/catch and dumping the stack trace if you can't >>> locate it easily. Alternatively, I think the test execution dumps may >>> carry a full stack already? >>> >>> Dawid >>> >>> >>> On Tue, Feb 21, 2017 at 7:23 PM, Joel Bernstein <joels...@gmail.com> >>> wrote: >>> > >>> > A test I've just added is being ignored when it's being called with the >>> > -Dtestmethod. >>> > >>> > Here is the command line: >>> > >>> > ant test -Dtestcase=StreamExpressionTest >>> > -Dtestmethod=testSignifcantTermsStream >>> > >>> > >>> > Here are some snippets from the output: >>> > ------------------------------ >>> > ------------------------------ >>> > >>> > [junit4] 2> 6440 INFO >>> > >>> > (TEST-StreamExpressionTest.testSignifcantTermsStream-seed#[619661D6DA496076]) >>> > [ ] o.a.s.SolrTestCaseJ4 ###Ending testSignifcantTermsStream >>> > >>> > [junit4] IGNOR/A 0.18s | >>> > StreamExpressionTest.testSignifcantTermsStream >>> > >>> > [junit4] > Assumption #1: got: <false>, expected: is <true> >>> > >>> > .... >>> > >>> > [junit4] Tests summary: 1 suite, 1 test, 1 ignored (1 assumption) >>> > >>> > ------------------------------------- >>> > >>> > ------------------------------------- >>> > >>> > Is anyone else seeing this behavior or have any idea why this might be >>> > happening? >>> > >>> > >>> > >>> > Thanks >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org >>> For additional commands, e-mail: dev-h...@lucene.apache.org >>> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
