You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "schongloo (via GitHub)" <gi...@apache.org> on 2025/09/26 00:17:01 UTC
[PR] Debugging the Blue/Green e2e tests [flink-kubernetes-operator]
schongloo opened a new pull request, #1033:
URL: https://github.com/apache/flink-kubernetes-operator/pull/1033
<!--
*Thank you very much for contributing to the Apache Flink Kubernetes Operator - we are happy that you want to help us improve the project. To help the community review your contribution in the best possible way, please go through the checklist below, which will get the contribution into a shape in which it can be best reviewed.*
## Contribution Checklist
- Make sure that the pull request corresponds to a [JIRA issue](https://issues.apache.org/jira/projects/FLINK/issues). Exceptions are made for typos in JavaDoc or documentation files, which need no JIRA issue.
- Name the pull request in the form "[FLINK-XXXX] [component] Title of the pull request", where *FLINK-XXXX* should be replaced by the actual issue number. Skip *component* if you are unsure about which is the best component.
Typo fixes that have no associated JIRA issue should be named following this pattern: `[hotfix][docs] Fix typo in event time introduction` or `[hotfix][javadocs] Expand JavaDoc for PuncuatedWatermarkGenerator`.
- Fill out the template below to describe the changes contributed by the pull request. That will give reviewers the context they need to do the review.
- Make sure that the change passes the automated tests, i.e., `mvn clean verify` passes. You can read more on how we use GitHub Actions for CI [here](https://nightlies.apache.org/flink/flink-kubernetes-operator-docs-main/docs/development/guide/#cicd).
- Each pull request should address only one issue, not mix up code from multiple issues.
- Each commit in the pull request has a meaningful commit message (including the JIRA id)
- Once all items of the checklist are addressed, remove the above text and this checklist, leaving only the filled out template below.
**(The sections below can be removed for hotfixes of typos)**
-->
## What is the purpose of the change
The Flink Operator e2e tests for Blue/Green Deployments are currently disabled due to difficulties reproducing the errors encountered in the build pipeline. This ticket is to fix them.
- test_bluegreen_laststate.sh
- test_bluegreen_stateless.sh
Currently in the debugging stage of the test execution, full PR description coming shortly
--
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-unsubscribe@flink.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Debugging the Blue/Green e2e tests [flink-kubernetes-operator]
Posted by "maheepm-lyft (via GitHub)" <gi...@apache.org>.
maheepm-lyft commented on PR #1033:
URL: https://github.com/apache/flink-kubernetes-operator/pull/1033#issuecomment-3386784574
Hi @schongloo, I left a comment just now on the merged BlueGreen PR [here](https://github.com/apache/flink-kubernetes-operator/pull/969/files?file-filters%5B%5D=.java&show-viewed-files=true#r2417417622). Sorry to do this after the initial PR has been merged!
--
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-unsubscribe@flink.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Debugging the Blue/Green e2e tests [flink-kubernetes-operator]
Posted by "gyfora (via GitHub)" <gi...@apache.org>.
gyfora closed pull request #1033: Debugging the Blue/Green e2e tests
URL: https://github.com/apache/flink-kubernetes-operator/pull/1033
--
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-unsubscribe@flink.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org