[GitHub] [commons-graph] XenoAmess commented on pull request #2: add openjdk11 and openjdk14 for travis-ci scripts.

[GitBox <gi...@apache.org>]

XenoAmess commented on pull request #2:
URL: https://github.com/apache/commons-graph/pull/2#issuecomment-643604636


   > No objection from me, though someone needs to investigate the build errors (I think even jdk8 failed). Happy if it's merged as-is, or if we wait until the tests are fixed, then rebase/merge.
   > 
   > Thanks @XenoAmess !
   > 
   > Bruno
   
   Hi.
   This build error is not my fault.
   I have no interest in investigating the real reason / fix it, but I checked this repo can NEVER pass all of its junit tests since commit 967b9bed79f51040597d68ef98512a24b0e94e41m  .
   
   The details are in commons-dev mailing list's mail : `[commons-graph] branch master updated: Travis CI configuration.`
   As I said in mailing list, I'm really curious. I'll quote the key part of my opinion below.
   
   > 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?
   
   


----------------------------------------------------------------
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.

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