> This discussion requires another thread. Well I don't think so, as I think this thread aims for making travis-ci can pass. And test failures are the reason why it cannot pass ci for now. I don't see the value in creating another thread.
Btw: I tested (if my memory are correct, as I didn't make a log for it) the latest commit (fail) , the first commit at year 2012(fail), the first commit of the repo(pass), the first commit of year2011month10(fail), the first commit of year2011month7(fail), and I tried every version from year2011month7 back, and finally I get the last commit that can pass all junit tests be 967b9bed79f51040597d68ef98512a24b0e94e41m ,which is just 3 hours after the repo created. Btw2: Is it a usual thing in commons, for a repo's branch master can never pass its own junit tests for years? I'm new here, knowing nearly nothing about commons, and become very confused. Btw3: And do the users of this repo know about this? Gilles Sadowski <gillese...@gmail.com> 于2020年6月13日周六 上午9:52写道： > 2020-06-13 1:43 UTC+02:00, Xeno Amess <xenoam...@gmail.com>: > > Done. > > Environment win10, jdk8. > > Due to the binary search, the last pr in this repo who can pass all junit > > tests is commit 967b9bed79f51040597d68ef98512a24b0e94e41 , which is at > > 6/11/2011,10:43PM > > Suggest revert all changes after that time point, and track them one by > > one. > > This discussion requires another thread. > > Regards, > Gilles > > > A project which can never pass its own junit tests is > kindof.....confusing. > > And me myself will never consider about using it. > > > > > > > > Xeno Amess <xenoam...@gmail.com> 于2020年6月13日周六 上午7:27写道： > > > >> Two failures and one error actually. > >> I will try to fetch the latest commit who CAN pass junit test, using > >> binary search. > >> Will send mail when I finish. > >> > >> Gilles Sadowski <gillese...@gmail.com> 于2020年6月13日周六 上午6:21写道： > >> > >>> Hi. > >>> > >>> 2020-06-12 21:43 UTC+02:00, Amey Jadiye <ameyjad...@gmail.com>: > >>> > On Fri, Jun 12, 2020 at 4:40 PM Gilles Sadowski < > gillese...@gmail.com> > >>> > wrote: > >>> > > >>> >> 2020-06-12 12:32 UTC+02:00, Xeno Amess <xenoam...@gmail.com>: > >>> >> > Hi. > >>> >> > I see the current travis-ci scripts. > >>> >> > Do we really care only jdk8? > >>> >> > Should we also add at some other jdk versions, at least adding > >>> >> > openjdk11, > >>> >> > as it is a stable version? > >>> >> > Or this repo has some known bug on jdk11? > >>> >> > > >>> >> > >>> >> Before refining, we should get[1] a first build: > >>> >> https://travis-ci.org/github/apache/commons-graph > >>> > > >>> > +1 > >>> > maybe you can check and merge my one upgrade PR to check this. > >>> > https://github.com/apache/commons-graph/pull/1 > >>> > >>> I've merged the changes to see that Travis is set up, > >>> even though some unit tests are in error: Please have > >>> a look. > >>> > >>> Thanks, > >>> Gilles > >>> > >>> > > >>> > I don't see it on Travis though, maybe because I raised it before > >>> > travis > >>> > setup. > >>> > > >>> > Regards, > >>> > Amey > >>> > > >>> >> > >>> >> > >>> >> Gilles > >>> >> > >>> >> [1] https://issues.apache.org/jira/browse/INFRA-20413 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
