![]() Once we have nondistributable archives available on a private server that won't be a big problem anymore. Some of these ports might not be distributable. Or do we instead make a general rule (not based on size) that we don't keep a port installed if nothing depends on it? (If it's, say, 5 or fewer ports, uninstall them, otherwise leave them installed.) We could base the decision of whether to uninstall on how many ports would be uninstalled. Or do we have the buildbot uninstall not only the large ports but also all ports depending on them? That might be ok for geant, but would be bad for texlive-latex-extra, on which lots of things depend. For example, geant4.10.4 is not large, but it depends on geant4.10.4-data which is.ĭo we force the uninstallation of the large ports, leaving the ports depending on them broken, on the assumption that when the buildbot asks to install them again it will reinstall the dependencies and fix them? If we could have mpbb automatically uninstall large ports, it would free up a good deal of disk space. ![]() It's getting to the point where builds are failing because there's not enough free disk space, and I am manually uninstalling some of these ports on the buildbot workers to free up space. Here are some of the larger ports installed on the highsierra buildbot worker: ![]() This is supposed to speed up builds so that we don't waste time constantly downloading and installing ports that are dependencies of a lot of other ports.īut there are also some inordinately large ports, such as some games, which aren't commonly used as dependencies. Our buildbot setup currently keeps all built ports installed on each worker. ![]()
0 Comments
Leave a Reply. |