uschindler commented on PR #12681: URL: https://github.com/apache/lucene/pull/12681#issuecomment-1763370765
In addition to that, maybe we should change TestVectorUtilSupport to spawn 3 child JVMs and don't set the property top-level? The problem is currently any of those: - If we enable the system properties globally without above patch, Jenkins tests would suddenly get slow (unless it happily use the correct bitsize fitting CPU) - If we apply my patch, normal Lucene tests would always use the unoptimized panama code. In that case we could also run jenkins tests without `--add-modules` If we run the TestVectorUtilSupport tests in 3 JVMs, the normal lucene tests would run with platform default settings (without overrides) and only the relevant tests checks all bit sizes and enforces integer vectors in separate JVMs. I would prefer this. -- 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
