xintongsong commented on pull request #15599:
URL: https://github.com/apache/flink/pull/15599#issuecomment-826292351
@galenwarren,
In most cases, I pull the codes to review them, but not necessarily build
them. For this time, I tried build your codes locally and have not run into any
problems.
I checked the logs, and it seems there's a connectivity issue between the
azure worker and google maven mirror.
This is a bit complicated. In short, IIUC, the problem should gone once we
fix the license issues.
- We have two worker pools for our ci build.
- The `compile_ci` stage is executed on Alibaba hosted machines,
downloading artifacts from Alibaba mirror. All artifacts can be properly
downloaded, thus the license checking fails in 20+ minutes which is after
downloading the `grpc` dependencies.
- The `e2e_ci` stage is executed on Azure hosted machines, downloading
artifacts from google mirror. The error happens in about 5 minutes,
complaining about not finding the dependency. I think it's a connectivity issue
because I tried downloading the same artifact from the same google mirror on my
local machine and it succeed.
- We leverage Azure cache for sharing maven dependency artifacts across
builds. That means, for all dependencies that have been downloaded previously,
they are fetched from azure cache rather than downloaded again from the maven
mirror. That's probably why the `e2e_ci` build does not fail for other
artifacts. This can be confirmed from the maven log, where no "Downloading xxx"
can be found until the failure.
I'll find people to look into the connectivity issue between google mirror
and azure workers. Meantime, I think once we fix the license issues and make
the `compile_ci` stage pass, the new dependencies should be uploaded to the
azure cache, and we should no longer have this error.
--
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.
For queries about this service, please contact Infrastructure at:
[email protected]
