-
Notifications
You must be signed in to change notification settings - Fork 701
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
{tools}[GCCcore/11.3.0] JupyterHub v3.0.0, configurable-http-proxy v4.5.3 w/ Python 3.10.4 #16424
{tools}[GCCcore/11.3.0] JupyterHub v3.0.0, configurable-http-proxy v4.5.3 w/ Python 3.10.4 #16424
Conversation
…http-proxy-4.5.3-GCCcore-11.3.0.eb
…asyconfigs into 20221017182151_new_pr_JupyterHub300
This comment was marked as outdated.
This comment was marked as outdated.
…ter-resource-usage.
…etween jupyterlmod, jupyter-resource-usage and jupyter-server-proxy
…source-usage. Did that now
This comment was marked as outdated.
This comment was marked as outdated.
…ine in jupyter-server. Add binutils to jupyterlmod as builddep.
@casparvl I saw this error:
I know there have been changes in this area of late - do I need to rebuild anything? |
@verdurin I'm not sure, for me it just works. If anything, it's probably the OpenSSL 1.1 dependency. As you may know, this can either just wrap your system OpenSSL or install one from EasyBuild. Maybe it wrapped your system OpenSSL and that fails to provide some symbol? I'm not sure... Anyway, I'll upload two test reports from our systems. Not sure if that's enough to convince you ;-) If not, you might look into rebuilding OpenSSL (maybe the system version underneath got updated?) and see if that helps. Or maybe we you can force N.B. I checked, and on our systems OpenSSL-1.1 wraps our system install. That means that
i.e.
so in our libcrypto, there are OPENSSL_1_1_0 symbols... maybe check which libcrypto it is picking upt for you, and if it contains the OPENSSL_1_1_0 symbols? |
Test report by @casparvl |
Test report by @casparvl |
easybuild/easyconfigs/j/jupyterlmod/jupyterlmod-3.0.0-GCCcore-11.3.0.eb
Outdated
Show resolved
Hide resolved
Test report by @boegelbot |
…epend on JupyterLab, nor on JupyterHub, since it can be used with either of those. Thus, lowered this to IPython.
…epend on JupyterLab, nor on JupyterHub, since it can be used with either of those. Thus, lowered this to IPython.
@boegelbot please test @ generoso |
@boegelbot please test @ jsc-zen2 |
@casparvl: Request for testing this PR well received on jsczen2l1.int.jsc-zen2.easybuild-test.cluster PR test command '
Test results coming soon (I hope)... - notification for comment with ID 1427877694 processed Message to humans: this is just bookkeeping information for me, |
Test report by @boegelbot |
Test report by @verdurin |
Here's where it failed for me:
|
@boegelbot: please test @ generoso |
@lexming: Request for testing this PR well received on login1 PR test command '
Test results coming soon (I hope)... - notification for comment with ID 1427953692 processed Message to humans: this is just bookkeeping information for me, |
Test report by @boegelbot |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@verdurin can you test again please? |
@boegelbot please test @ jsc-zen2 |
@lexming: Request for testing this PR well received on jsczen2l1.int.jsc-zen2.easybuild-test.cluster PR test command '
Test results coming soon (I hope)... - notification for comment with ID 1427985339 processed Message to humans: this is just bookkeeping information for me, |
Test report by @boegelbot |
Test report by @casparvl |
Test report by @casparvl |
Test report by @verdurin |
A different failure for me this time, the same one mentioned above regarding OpenSSL:
|
Test report by @verdurin |
@verdurin can you check the contents of your
|
@verdurin since it is unlikely that your failed tests are related to the changed in this PR I'll go ahead and merge it before it gets lost in my memory stack 🙂 |
Going in, thanks @casparvl ! |
(created using
eb --new-pr
)