morazow commented on code in PR #182: URL: https://github.com/apache/flink-docker/pull/182#discussion_r1507732247
########## .github/workflows/ci.yml: ########## @@ -17,14 +17,22 @@ name: "CI" on: [push, pull_request] +env: + TAR_URL: "https://s3.amazonaws.com/flink-nightly/flink-1.20-SNAPSHOT-bin-scala_2.12.tgz"; + jobs: ci: + name: CI using JDK ${{ matrix.java_version }} runs-on: ubuntu-latest + strategy: + fail-fast: false + max-parallel: 1 Review Comment: > > #11 8.399 + /bin/bash /opt/flink/bin/config-parser-utils.sh /opt/flink/conf /opt/flink/bin /opt/flink/lib -repKV rest.address,localhost,0.0.0.0 -repKV rest.bind-address,localhost,0.0.0.0 -repKV jobmanager.bind-host,localhost,0.0.0.0 -repKV taskmanager.bind-host,localhost,0.0.0.0 -rmKV taskmanager.host=localhost > > #11 8.625 sed: can't read /config.yaml: No such file or directory > > I forgot that we're also doing testing. Maybe, there's something odd with the config modification logic (see [workflow log](https://github.com/morazow/flink-docker/actions/runs/8081181748/job/22079149028#step:4:8838))? Yes, tests have these kind of issues. Another ones: ``` WARNING: attempted to load jemalloc from /usr/lib/x86_64-linux-gnu/libjemalloc.so but the library couldn't be found. glibc will be used instead. ./docker-entrypoint.sh: line 80: /home/runner/work/flink-docker/flink-docker/testing/bin/config-parser-utils.sh: No such file or directory jemalloc was enabled but it was not found in the system. LD_PRELOAD is unchanged and glibc will be used instead. ./docker-entrypoint.sh: line [8](https://github.com/morazow/flink-docker/actions/runs/8096433961/job/22125972877#step:4:9)0: /home/runner/work/flink-docker/flink-docker/testing/bin/config-parser-utils.sh: No such file or directory ``` But that line still happens when it is green also. Here the success run: https://github.com/morazow/flink-docker/actions/runs/8096433961/job/22125972520 -- 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: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
