Andy, I’m working on cleaning up the warnings in the unit tests, and had the same questions about how to tell if things are broken or not.
https://ci-builds.apache.org/job/Solr/job/Solr-Check-main/ is my first stop. Take a look at http://fucit.org/solr-jenkins-reports/failure-report.html <http://fucit.org/solr-jenkins-reports/failure-report.html> and http://fucit.org/solr-jenkins-reports/history-trend-of-recent-failures.html <http://fucit.org/solr-jenkins-reports/history-trend-of-recent-failures.html> as well... Eric > On Jul 2, 2022, at 10:27 AM, Andy Lester <a...@petdance.com> wrote: > >> +1 to what Christine said, and thanks for volunteering to take it off >> my list Andy. If you do push up a PR and no one jumps on it, feel >> free to plug it here and I'll definitely take a look. > > I will start digging into this. > > My big concern is I don’t know what to do as far as testing. Last time I went > poking around in the code and tried to remove some old stuff, I found the > test suite failed some tests, and I was told that some of the tests are known > to fail, and not to worry about it. Is there somewhere I can get an idea of > how I can tell if I’ve broken something or not? > > Thanks, > Andy _______________________ Eric Pugh | Founder & CEO | OpenSource Connections, LLC | 434.466.1467 | http://www.opensourceconnections.com <http://www.opensourceconnections.com/> | My Free/Busy <http://tinyurl.com/eric-cal> Co-Author: Apache Solr Enterprise Search Server, 3rd Ed <https://www.packtpub.com/big-data-and-business-intelligence/apache-solr-enterprise-search-server-third-edition-raw> This e-mail and all contents, including attachments, is considered to be Company Confidential unless explicitly stated otherwise, regardless of whether attachments are marked as such.
