Skip to content
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

Dockerfile build fails on livy-server step #408

Open
brunolnetto opened this issue Jun 23, 2023 · 3 comments
Open

Dockerfile build fails on livy-server step #408

brunolnetto opened this issue Jun 23, 2023 · 3 comments

Comments

@brunolnetto
Copy link

brunolnetto commented Jun 23, 2023

Hi,

I try host locally this solution for apache spark on its language flavors with command run docker build -t livy-ci dev/docker/livy-dev-base/. After some installation steps, the error log appers on terminal. I attempt on Linux Ubuntu 20.04.

[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO] 
[INFO] Livy Project Parent POM ............................ SUCCESS [01:26 min]
[INFO] livy-api ........................................... SUCCESS [03:30 min]
[INFO] livy-client-common ................................. SUCCESS [  4.819 s]
[INFO] livy-test-lib ...................................... SUCCESS [  2.996 s]
[INFO] multi-scala-project-root ........................... SUCCESS [  1.042 s]
[INFO] livy-core-parent ................................... SUCCESS [  0.177 s]
[INFO] livy-core_2.11 ..................................... SUCCESS [  9.340 s]
[INFO] livy-rsc ........................................... SUCCESS [ 50.358 s]
[INFO] livy-repl-parent ................................... SUCCESS [ 25.652 s]
[INFO] livy-repl_2.11 ..................................... SUCCESS [04:05 min]
[INFO] livy-server ........................................ FAILURE [ 48.405 s]
[INFO] livy-assembly ...................................... SKIPPED
[INFO] livy-client-http ................................... SKIPPED
[INFO] livy-scala-api-parent .............................. SKIPPED
[INFO] livy-scala-api_2.11 ................................ SKIPPED
[INFO] livy-integration-test .............................. SKIPPED
[INFO] livy-coverage-report ............................... SKIPPED
[INFO] livy-examples ...................................... SKIPPED
[INFO] livy-python-api .................................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 11:26 min
[INFO] Finished at: 2023-06-22T21:17:57+00:00
[INFO] Final Memory: 108M/1364M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project livy-server: Could not resolve dependencies for project org.apache.livy:livy-server:jar:0.8.0-incubating-SNAPSHOT: Failed to collect dependencies at io.dropwizard.metrics:metrics-healthchecks:jar:3.1.0: Failed to read artifact descriptor for io.dropwizard.metrics:metrics-healthchecks:jar:3.1.0: Could not transfer artifact io.dropwizard.metrics:metrics-healthchecks:pom:3.1.0 from/to central (https://repo1.maven.org/maven2): Connection reset -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <goals> -rf :livy-server
@brunolnetto brunolnetto changed the title Dockerfile build failts on ilvy-server step Dockerfile build fails on livy-server step Jun 23, 2023
@mvanderlee
Copy link
Contributor

I'm running into the same issue. These are 2 failing tests:

BatchSessionSpec:                                                                                                                                                                                                                                                                 
A Batch process                                                                                                                                                                                                                                                                   
- should create a process *** FAILED *** (1 second, 30 milliseconds)                                                                                                                                                                                                              
  false was not true (BatchSessionSpec.scala:94)


BatchServletSpec:
Batch Servlet
- should create and tear down a batch *** FAILED *** (1 second, 118 milliseconds)
  false was not true (BatchServletSpec.scala:121)

@mvanderlee
Copy link
Contributor

@brunolnetto I found the issue.
The tests include Python2 code that doesn't work in Python3.
i.e: print "hello world" instead of print("hello world")

The fix is to write the lines for Python3:
https://github.com/apache/incubator-livy/blob/master/server/src/test/scala/org/apache/livy/server/batch/BatchSessionSpec.scala#L51
https://github.com/apache/incubator-livy/blob/master/server/src/test/scala/org/apache/livy/server/batch/BatchServletSpec.scala#L46

@brunolnetto
Copy link
Author

brunolnetto commented Sep 27, 2023

Noice! Someone should notify Apache, Python 2 is being deprecated

ksumit pushed a commit that referenced this issue Oct 24, 2023
Fix print statement in tests to be Python 2 and Python 3 compatible. #408
jimenefe pushed a commit to onedot-data/incubator-livy that referenced this issue Oct 15, 2024
Fix print statement in tests to be Python 2 and Python 3 compatible. apache#408
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants