vvcephei commented on pull request #9471:
URL: https://github.com/apache/kafka/pull/9471#issuecomment-718826291
Ok, I've run it a total of 5 times now, and it has passed two times and
timed out three times.
I did some analysis on the timed out logs, and found that every test that
started either passed or got skipped. I was hoping to find a test that hung,
but no luck.
For example, I downloaded the logs for run 1, which timed out as
`timeout-1.txt`:
```bash
[john@arcturus Downloads]$ cat timeout-1.txt | grep STARTED | sed 's|^\[\S*]
||' | sed 's/ STARTED//' | sort > /tmp/1-started
[john@arcturus Downloads]$ cat timeout-1.txt | grep PASSED | sed 's|^\[\S*]
||' | sed 's/ PASSED//' | sort > /tmp/1-passed
[john@arcturus Downloads]$ cat timeout-1.txt | grep SKIPPED | sed 's|^\[\S*]
||' | sed 's/ SKIPPED//' | sort > /tmp/1-skipped
[john@arcturus Downloads]$ wc -l /tmp/1-skipped /tmp/1-passed
61 /tmp/1-skipped
10891 /tmp/1-passed
10952 total
[john@arcturus Downloads]$ wc -l /tmp/1-started
10952 /tmp/1-started
```
Since all the other builds in all the other branches are working with
effectively the same Jenkinsfile, I'm deeply suspicious that there actually is
something wrong with the 2.6 codebase and not this PR itself.
I think we should go ahead and merge this in some form. I could see:
1. Just merge this as-is and file a Jira ticket to investigate why java 11
builds time out on 2.6.
2. Exclude java 11 from the jenkinsfile and go ahead and merge with just
java 8 and 14.
WDYT, @omkreddy @jolshan @ijuma ?
----------------------------------------------------------------
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:
us...@infra.apache.org
