-
Notifications
You must be signed in to change notification settings - Fork 446
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
update_versions: add --noconfirm option #4996
Conversation
@davidpanderson, for some reason server integration tests is failing trying to connect to the server running in docker container. |
I'm seeing the following, which looks like a server is down:
4964> Task :app:javaPreCompileArmv6_debug FAILED
4965FAILURE: Build failed with an exception.
4966
4967* What went wrong:
4968Execution failed for task ':app:javaPreCompileArmv6_debug'.
4969> Could not resolve all files for configuration
':app:_agp_internal_javaPreCompileArmv6_debug_kaptClasspath'.
4970 > Could not resolve com.google.dagger:dagger-compiler:2.44.
4971 Required by:
4972 project :app
4973 > Could not resolve com.google.dagger:dagger-compiler:2.44.
4974 > Could not get resource
'https://repo.maven.apache.org/maven2/com/google/dagger/dagger-compiler/2.44/dagger-compiler-2.44.pom'.
4975 > Could not GET
'https://repo.maven.apache.org/maven2/com/google/dagger/dagger-compiler/2.44/dagger-compiler-2.44.pom'.
4976 > Connect to repo.maven.apache.org:443
[repo.maven.apache.org/146.75.28.215] failed: Connect timed out
4977
4978* Try:
4979> Run with --stacktrace option to get the stack trace.
4980> Run with --info or --debug option to get more log output.
4981> Run with --scan to get full insights.
4982
4983* Get more help at https://help.gradle.org
4984
4985BUILD FAILED in 2m 40s
498616 actionable tasks: 15 executed, 1 up-to-date
4987Error: Process completed with exit code 1.
Build libs
0s
Build apps
0s
Build manager with vcpkg
0s
Build libs with vcpkg
0s
Build apps with vcpkg
0s
Build libs with cmake
0s
Prepare logs on failure
0s
Upload logs on failure
0s
Prepare artifacts for deploy
0s
Upload generic artifacts
0s
Upload xiaomi manager
0s
Upload armv6 only manager
0s
Upload JUnit Tests Results
0s
Upload coverage report
0s
Post Cache dependencies
0s
Post Setup Java
0s
Post Run ***@***.***
0s
Complete job
0s
update_versions: add --noconfirm option · ***@***.***
…On Sat, Nov 5, 2022 at 9:51 AM Vitalii Koshura ***@***.***> wrote:
@davidpanderson, for some reason server integration tests is failing trying to connect to the server running in docker container.
I assume this happens because server instance was not created properly.
Could you please check this somehow and fix?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Not sure this is really related: I tried to rerun and it always fails on this PR and never fails on any other without this change. |
That's odd - the automated build AFAIK doesn't involve this file. |
It's done while building BOINC server via docker: https://github.com/marius311/boinc-server-docker/blob/28df02f75c07650c53a7c5f0a389118f48698fda/images/makeproject/makeproject-step2.sh#L63 |
Oops!! I accidentally made it non-executable. Fixed now. |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #4996 +/- ##
============================================
- Coverage 10.83% 10.83% -0.01%
Complexity 1064 1064
============================================
Files 279 279
Lines 35994 35995 +1
Branches 8127 8127
============================================
Hits 3899 3899
- Misses 31706 31707 +1
Partials 389 389
|
@lfield, would be nice if you could review this as well. |
LGTM |
No description provided.