Hi,
You may have to manually cleanup old directories on your buildbot
workers. Sorry, I don't know the process how to do that. If someone
finds a way, please share it!
--
To be able to support multiple similar jobs on the same buildbot
worker, the build prefixes have been modified last week:
htt
Le ven. 27 sept. 2019 à 15:14, David Edelsohn a écrit :
> Hi, Victor
>
> Where, exactly, should I look for abandoned build directories?
It's in the directory configured in your buildbot client. Example with
the Fedora Rawhide worker:
buildbot@python-builder-rawhide$ pwd
/home/buildbot/buildarea
Is this only an issue for systems with Clang installed? I don't see
that range of names on any of my workers.
Thanks, David
On Fri, Sep 27, 2019 at 9:36 AM Victor Stinner wrote:
>
> Le ven. 27 sept. 2019 à 15:14, David Edelsohn a écrit :
> > Hi, Victor
> >
> > Where, exactly, should I look for
Not all workers are impacted, impacted Python classes:
* PGOUnixBuild: Profile Guided Optimization (PGO)
* ClangUbsanLinuxBuild: clang "UB sanitizer"
* ClangUnixInstalledBuild: clang
* LTONonDebugUnixBuild: Link Time Optimization (LTO)
* LTOPGONonDebugBuild: LTO + PGO
Victor
Le ven. 27 sept. 201
On Fri, Sep 27, 2019 at 8:40 AM David Edelsohn wrote:
>
> Is this only an issue for systems with Clang installed? I don't see
> that range of names on any of my workers.
If you don't mind the bandwidth to check things out fresh again and
don't want to try to track down which ones are still neces
