echauchot commented on PR #37:
URL: 
https://github.com/apache/flink-connector-cassandra/pull/37#issuecomment-3306333646

   > > > > > @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.
   > > 
   > > 
   > > Well, even 10 min timeout is not enough to start 2 containers on the 
github CI ! Locally all tests run in 2 min including the startup time. I might 
change my plans (not start in parallel or change the wait condition) to make it 
pass on github CI
   > 
   > I ran the change on my local (> 10 times) and it succeeded every time. 
Pretty sure it is a CI issue 😄 @echauchot
   
   Yes, github actions is a shared environment so pretty loaded. 
   With 2 containers starting in sequence instead of parallel and a 3 minutes 
startup timeout, it passes on the Github CI.
   For some (strange) reason, this PR automatically links to the build of a 
very old commit. Here is the link to the build of the last commit of the PR: 
https://github.com/echauchot/flink-connector-cassandra/runs/50669333696
   It is all green, so I'll merge the PR as you already approved it.
   


-- 
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

Reply via email to