similar to: llvm.org/docs/ stopped updating

On 08/01/2018 19:16, Matthias Braun wrote: > I believe the results of the docu generation can be found here: > > http://lists.llvm.org/pipermail/www-scripts/2018-January/thread.html > > (though a nice improvement for the future would be to make this into a > buildbot or jenkins job so people would get direct blame mails) > Thanks Matthias. I had a look at the error

I believe the results of the docu generation can be found here: http://lists.llvm.org/pipermail/www-scripts/2018-January/thread.html <http://lists.llvm.org/pipermail/www-scripts/2018-January/thread.html> (though a nice improvement for the future would be to make this into a buildbot or jenkins job so people would get direct blame mails) - Matthias > On Jan 8, 2018, at 10:27 AM,

I will get this fixed today. Sorry I have been dealing with some family stuff yesterday. -Tanya > On Jan 9, 2018, at 9:58 AM, Florian Hahn <florian.hahn at arm.com> wrote: > > > >> On 08/01/2018 19:16, Matthias Braun wrote: >> I believe the results of the docu generation can be found here: >>

I have fixed the issue. It was due to my addition of the new opcode documentation generation script and some permissions got changed. -Tanya > On Jan 9, 2018, at 10:15 AM, Tanya Lattner <tanyalattner at llvm.org> wrote: > > I will get this fixed today. Sorry I have been dealing with some family stuff yesterday. > > -Tanya > >> On Jan 9, 2018, at 9:58 AM, Florian

Hi I am trying to build  the documentation and view it as html. When I ran the `make docs-llvm-html` target but ran into this below issue. Has anyone faced this issue? ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- % make

Hi, working on the LNT documentation I am wondering about a few things: - LNT documentation recommends to do `easy_install lnt==0.4.2dev` (in the install box on the left side of the title page). The last available version of LNT on pypy is version 0.4.0 from 2012. Are there plans to keep this up to date or should we better remove the entry and not mention pypy packages anymore? - Building the

I'd be fine pulling the pypi (sic) entry, shall I make it so? - Daniel On Tue, Jul 18, 2017 at 11:06 AM Chris Matthews <chris.matthews at apple.com> wrote: > Yep, we should pull that package down, or start to update it. > > The docs builds work for me. Is it possible that is not in your venv or > something like that? > > > On Jul 18, 2017, at 10:48 AM, Matthias

I updated the docs to show a pip/svn install like this: pip install svn+http://llvm.org/svn/llvm-project/lnt/trunk <svn+http://llvm.org/svn/llvm-project/lnt/trunk> > On Jul 18, 2017, at 11:24 AM, Kristof Beyls <kristof.beyls at arm.com> wrote: > > >> On 18 Jul 2017, at 20:21, Daniel Dunbar <daniel at zuster.org <mailto:daniel at zuster.org>> wrote:

On Thu, Sep 24, 2020 at 07:26:01PM +0200, Karol Herbst wrote: > On Thu, Sep 24, 2020 at 6:03 PM Jeremy Cline <jcline at redhat.com> wrote: > > > > On Wed, Sep 23, 2020 at 11:36:54PM +0200, Karol Herbst wrote: > > > On Wed, Sep 23, 2020 at 10:39 PM Jeremy Cline <jcline at redhat.com> wrote: > > > > > > > > On Wed, Sep 23, 2020 at

Hi, TL;DR - We should update the bot(s) responsible for building the LLVM documentation so that they use recommonmark 0.5.0, and apply https://reviews.llvm.org/D63211. Full context: I recently started trying to build the sphinx docs. However, a change by Jordan (r363100) resulted in me no longer being able to build them, even though the build bots were green and he could build them himself.

On Wed, Sep 23, 2020 at 11:36:54PM +0200, Karol Herbst wrote: > On Wed, Sep 23, 2020 at 10:39 PM Jeremy Cline <jcline at redhat.com> wrote: > > > > On Wed, Sep 23, 2020 at 09:02:45PM +0200, Karol Herbst wrote: > > > On Fri, Sep 11, 2020 at 6:21 PM Jeremy Cline <jcline at redhat.com> wrote: > > > > <snip> > > > > > yeah, I think

> On 3 Apr 2017, at 22:47, Alex Denisov <1101.debian at gmail.com> wrote: > > The HTML generated using sphinx[1]. > At the bottom of each page you can see actual version of sphinx used to generate this page. > Thanks -- interesting that the docs haven't been updated since March 15th: © Copyright 2003-2017, LLVM Project. Last updated on 2017-03-16. Created using Sphinx

Hi -- I've recently added some documentation to the LLVM docs subdirectory, and was wondering about a couple of things: - How should I best debug whether the docs (in RST) are syntactically correct? Are there recommended practices for doing a sanity check on the docs? - How often do the documents get built and uploaded to the website? Cheers -- Dean

On 3 April 2017 at 13:59, Daniel Berlin via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > > On Mon, Apr 3, 2017 at 5:51 AM, Dean Michael Berris via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> >> >> On 3 Apr 2017, at 22:47, Alex Denisov <1101.debian at gmail.com> wrote: >> >> The HTML generated using sphinx[1]. >> At the

Daniel, Tobias, Renato and myself have been looking a little bit at the potential underlying reason for why http://llvm.org/perf/ is instable, and have found some clues. I want to share them here to give people with more experience in the frameworks used by LNT (flask, sqlalchemy, wsgi, .) a chance to check if our reasoning below seems plausible. Daniel noticed the following backtrace in the

Last night, I triggered a buildbot error after my most recent commit. That one was totally on me as the warning did pop up while generating the docs site locally using the sphinx-build command (confirmed this afternoon). I just checked in a commit to resolve the error but now it appears I've triggered a different buildbot error? This error did not come up when I built the site locally to test

Hi all, It looks like the llvm-sphinx-docs fails for a long time (at least 20 days). Can someone please confirm if this is true? Best regards, Djordje

On 7 April 2017 at 15:50, Tanya Lattner <tanyalattner at llvm.org> wrote: > So, building the docs isn't the issue I feel is the problem. The script we > have works totally fine. The problem is people breaking the docs. > > So how is this better? I don't know enough about the website, but there are other problems in our infrastructure: * We need to manually update

Hi everyone. My name is DeForest Richards. I’m the technical writer who was selected to work on the LLVM project as part of the Google Season of Docs program. I’ll be helping to restructure the documentation page(s) to make it easier for new and existing users to navigate the LLVM docs. I’m currently reviewing the existing docs, so you’ll probably see me posting questions over the next several

> > After using 'python sdist', can't you use the tarball (in python/dist) > > in order to create a venv directly? > > I think I will be able to install the python library in the venv using > the tarball. However, won't my liguestfs application require some of > the binaries installed as part of 'make install' for running? I am > trying to not