Ticket for gitpod usability improvements: https://trac.sagemath.org/ticket/33113
On Monday, February 14, 2022 at 2:01:29 AM UTC-8 Dima Pasechnik wrote: > Hi, > I'm testing this on a ticket, and noticed that the Ubuntu host it runs > on has Linuxbrew installed. > > gitpod /workspace/sagetrac-mirror (public/build/github_build) $ which brew > /home/linuxbrew/.linuxbrew/bin/brew > As a result, ./configure thinks it's a Homebrew macOS system... > (This is e.g. trac 32753 - not worked on yet) > > Perhaps, if possible, not having Linuxbrew on the host might be a good > idea, for the time being. > > Dima > > On Mon, Feb 14, 2022 at 12:15 AM Matthias Koeppe > <matthia...@gmail.com> wrote: > > > > Thanks a lot for this work, Tobias! Glad to see that it is merged now. > > > > I have added a bit based on your posting to > https://wiki.sagemath.org/ReleaseTours/sage-9.6 > > > > > > On Sunday, February 13, 2022 at 1:26:06 PM UTC-8 tobias...@gmail.com > wrote: > >> > >> Hi everyone, > >> > >> as you probably have already seen, there are a few new status badges in > the trac ticket display. > >> We have now: > >> 1. Linter that checks that the code of the current branch adheres to > the style guidelines. In order to see details when it fails, you can click > on it and then select the most recent workflow run. (This already exists > for a while) > >> 2. Buid & test that builds sage for the current branch (incrementally > on top of the system packages of the develop branch) and runs the test. > Details are again available by clicking on the badge. (This is currently > still gray until https://trac.sagemath.org/ticket/33263 is merged into > master) > >> 3. Build documentation workflow that builds the documentation for the > current branch. If you click on it, you get the html output of the > successful run. The idea is to use this to easily inspect changes to the > documentation without the need to locally rebuild the docs yourself. If the > doc build fails, you can go to > https://github.com/sagemath/sagetrac-mirror/actions/workflows/doc-build.yml > and choose the particular branch to see what went wrong. > >> 4. Open in gitpod. This will spin up a pre-configured dev environment > in the browser (based on VS code), where the branch is already checked-out > and everything is pre-build. Feel free to use it to quickly check that the > changes in the ticket work as expected or to even make further changes > yourself. To find out more: https://www.gitpod.io/ > >> > >> The idea is that these three status badges complement the existing > patchbots (and maybe even replace them in the future). In particular, they > are supposed to always be green. Please keep this in mind when reviewing a > ticket. > > > > -- > > You received this message because you are subscribed to the Google > Groups "sage-devel" group. > > To unsubscribe from this group and stop receiving emails from it, send > an email to sage-devel+...@googlegroups.com. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/sage-devel/fa011350-6b93-40e2-948d-a88bce053c35n%40googlegroups.com > . > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/f131fbdb-4af2-498a-8ef6-04233b0e4370n%40googlegroups.com.
