echauchot commented on PR #37: URL: https://github.com/apache/flink-connector-cassandra/pull/37#issuecomment-3311556081
> > > @Poorvankbhatia I have the impression that there is a build result cache issue on github. The build is not finished but the previous built is printed on screen > > > > > > yeah it is still finding the `cassandraContainer ` variable. Is there no way to clear these build caches? Do u see any such field in the actions tab? > > it is like it was showing a very old build on a old commit (before adding the second container). At least I can link to the correct github actions builds from my IDE with the github plugin. > > I have already checked the github actions cache and the only things I see are the [flink-binaries](https://issues.apache.org/jira/browse/FLINK-binaries) (not related as it is [flink-core](https://issues.apache.org/jira/browse/FLINK-core)) and setup-java-Linux-x64-maven*. I'll try to remove the later. > > Anyway I see in the regular build that the startup of both containers to not fit in the 3 min graceful timeout. @Poorvankbhatia I understood the Github build issue: it is not a cache issue as we supposed, it is just due to the fact that I merged your SQL PR to main and that PR references the old cassandraContainer. Github tests the current PR by doing a rebase on main. This rebase does not fail because there are no conflicts, it just adds my changes on top of yours. Hence the `cassandraContainer ` variable that is left in the code and the compilation issue. I'll manually rebase onto main and replace cassandraContainer by cassandraContainer1 in you code. -- 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
