tim-patterson commented on pull request #11760:
URL: https://github.com/apache/kafka/pull/11760#issuecomment-1049161045


   > The most recent [system test run on 
trunk](http://confluent-kafka-system-test-results.s3-us-west-2.amazonaws.com/2022-02-09--001.system-test-kafka-trunk--1644413755--confluentinc--master--753251b0f6/report.html)
 I could find on Jenkins was one on February 9th. This run does not contain the 
system test failures [I mentioned 
above](http://confluent-kafka-branch-builder-system-test-results.s3-us-west-2.amazonaws.com/2022-02-21--001.system-test-kafka-branch-builder--1645479435--tim-patterson--KAFKA-13600-2--7b1e8797de/report.html).
   > 
   > @tim-patterson Can you consistently reproduce the failures locally on 
trunk?
   
   Yes I seem to be able to, they're all timeout failures so maybe the extra 
latency of waiting for acks=all is enough to tip it over a timeout locally...
   
   So here's a trunk commit from yesterday
   
   ```
   tpatterson@Tims-MacBook-Pro-2 kafka % git status
   On branch trunk
   Your branch is up to date with 'origin/trunk'.
   
   nothing to commit, working tree clean
   tpatterson@Tims-MacBook-Pro-2 kafka % git log --oneline | head -n2
   a5bb45c11a KAFKA-13511: Add support for different unix precisions in 
TimestampConverter SMT (#11575)
   576496a1ca MINOR: Improve Connect docs (#11642)
   
   tpatterson@Tims-MacBook-Pro-2 kafka % tests/docker/ducker-ak down && 
./gradlew clean && REBUILD="t" 
TC_PATHS="tests/kafkatest/tests/streams/streams_cooperative_rebalance_upgrade_test.py::StreamsCooperativeRebalanceUpgradeTest.test_upgrade_to_cooperative_rebalance"
 _DUCKTAPE_OPTIONS='--parameters '\''{"upgrade_from_version":"0.10.0.1"}'\' 
bash tests/docker/run_tests.sh
   
   ...
   
   
================================================================================
   SESSION REPORT (ALL TESTS)
   ducktape version: 0.8.1
   session_id:       2022-02-23--001
   run time:         2 minutes 21.028 seconds
   tests run:        1
   passed:           0
   failed:           1
   ignored:          0
   
================================================================================
   test_id:    
kafkatest.tests.streams.streams_cooperative_rebalance_upgrade_test.StreamsCooperativeRebalanceUpgradeTest.test_upgrade_to_cooperative_rebalance.upgrade_from_version=0.10.0.1
   status:     FAIL
   run time:   2 minutes 20.921 seconds
   
   
       TimeoutError("Never saw 'Processed [0-9]* records so far' message 
ducker@ducker07")
   Traceback (most recent call last):
     File 
"/usr/local/lib/python3.9/dist-packages/ducktape/tests/runner_client.py", line 
133, in run
       data = self.run_test()
     File 
"/usr/local/lib/python3.9/dist-packages/ducktape/tests/runner_client.py", line 
190, in run_test
       return self.test_context.function(self.test)
     File "/usr/local/lib/python3.9/dist-packages/ducktape/mark/_mark.py", line 
429, in wrapper
       return functools.partial(f, *args, **kwargs)(*w_args, **w_kwargs)
     File 
"/opt/kafka-dev/tests/kafkatest/tests/streams/streams_cooperative_rebalance_upgrade_test.py",
 line 93, in test_upgrade_to_cooperative_rebalance
       verify_running(processor, self.processing_message)
     File "/opt/kafka-dev/tests/kafkatest/tests/streams/utils/util.py", line 
19, in verify_running
       monitor.wait_until(message,
     File 
"/usr/local/lib/python3.9/dist-packages/ducktape/cluster/remoteaccount.py", 
line 707, in wait_until
       return wait_until(lambda: self.acct.ssh("tail -c +%d %s | grep '%s'" % 
(self.offset + 1, self.log, pattern),
     File "/usr/local/lib/python3.9/dist-packages/ducktape/utils/util.py", line 
41, in wait_until
       raise TimeoutError(err_msg() if callable(err_msg) else err_msg)
   ducktape.errors.TimeoutError: Never saw 'Processed [0-9]* records so far' 
message ducker@ducker07
   ```


-- 
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: jira-unsubscr...@kafka.apache.org

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


Reply via email to