uschindler commented on PR #13146:
URL: https://github.com/apache/lucene/pull/13146#issuecomment-1972777086

   > I'm not sure how you debugged that!
   
   I did not debug that; it was an observation and then try/error. I was a bit 
annoyed yesterday so here is my observations:
   
   - Jenkins did not fail (so it looks like on Jenkins/CI actions and the tests 
are not running with animated status display), all works fine and at end Gradle 
knows how many tests were execeuted and the condition "fail is zero" does not 
trigger. I cannot confirm that, but for some reason when running tests in CI 
this is not a problem.
   - If you run tests in your console with colored display and those Gradle 
animations, there was the following observation: The tests were running 
successfully, but the first line of Gradle output where the test counter is 
displayed stays at "0 tests". At end the build fails with error "no tests ran", 
although it spend minutes on (successfully) executing all test. If you enabled 
verbose test output, no execptions, nothing! -- but every test at end shows a 
reproduce line, but no failure error message or any stack trace.
   
   > I tried to debug what gradle is doing with this tests counter (hey, a 
stacktrace of the offending setAccessible would be nice), but I think @dweiss 
has seen this before, it is not really possible. As soon as you set 
java.security.debug on the test JVM, gradle test runner dies because it doesn't 
like the stderr prints or something?
   
   No idea. I was shortly before jumping out of the windows last night. I did 
not try to debug I just reverted test changes step by step until the policy 
file came to my mind....
   
   After reverting the changes there the test counter was incrementing again. I 
did not do any further investigations r debugging. I was just annoyed and angry 
and tired (2:30 in the morning).
   
   This is all bad, no debugging possible.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org

Reply via email to