-
-
Notifications
You must be signed in to change notification settings - Fork 553
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
Fix broken gitpod #34623
Comments
comment:1
The conda environment creation fails (
|
Branch: u/mkoeppe/fix_broken_gitpod |
New commits:
|
Commit: |
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
This comment has been minimized.
This comment has been minimized.
Author: Matthias Koeppe |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:12
Thanks for working on this.
Not sure what guesswork you mean, but the full logs can be found at https://gitpod.io/t/sagemath/sagetrac-mirror-1/prebuilds or directly in the browser if you trigger a prebuild using the magical url. The logs (https://gitpod.io/t/sagemath/sagetrac-mirror-1/41eac415-6e5a-41a3-9175-ac2fc463d659) for this branch indicate the following error
but I couldn't find which command triggered it. Another remark: Not sure if we really want to blow up the root folder by the additional gitpod scripts. Given that they should strongly simplify once we move to github (no extra trac nor ssh treatment will be necessary), I would propose to keep them inline. |
comment:14
Replying to Tobias Diez:
The one in https://groups.google.com/g/sage-devel/c/JIiytzMsLCU trying to diagnose based on error messages of commands that ran even though an earlier command failed. |
comment:15
Replying to Tobias Diez:
I moved it to separate scripts so that there is proper error handling. Whatever the gitpod folks do with the scripts, normal error handling is not working. |
comment:16
Replying to Tobias Diez:
Good point. I'll move that part to a separate script and see if I can keep the other things inline. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
comment:19
prebuild is still running but looking good |
comment:20
Replying to Tobias Diez:
Sure, but a problem is that when starting the gitpod, the terminal did not have enough scrollback, so one could not see the first error. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:22
Thanks for the quick follow-up. Code looks good to me, gitpod prebuild and actual start are working now again. So good to go. Could you please open an issue at the gitpod repo with your error handling problem. That should be fixed upstream. |
Reviewer: Tobias Diez |
comment:23
Thanks! |
comment:24
I've opened gitpod-io/gitpod#13508 |
comment:25
Thank you for fixing this immediately! Just to understand why it worked in former versions: The error has been triggered by the presence of |
comment:26
Yes, that's right. It's a mistake I made in that ticket - that conda package does exist, but only in the default channel, not in the conda-forge channel. |
comment:27
Replying to Matthias Köppe:
I see. Thanks! |
Changed branch from u/mkoeppe/fix_broken_gitpod to |
as reported in https://groups.google.com/g/sage-devel/c/JIiytzMsLCU
Here we
CC: @soehms @dimpase @tobiasdiez
Component: build
Author: Matthias Koeppe
Branch/Commit:
8b1063c
Reviewer: Tobias Diez
Issue created by migration from https://trac.sagemath.org/ticket/34623
The text was updated successfully, but these errors were encountered: