Opened 5 years ago
Last modified 4 years ago
#60124 assigned defect
swi-prolog-devel @8.1.22: swipl executable remains running after port installs
| Reported by: | ryandesign (Ryan Carsten Schmidt) | Owned by: | J.Wielemaker@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | Cc: | pmoura (Paulo Moura) | |
| Port: | swi-prolog-devel |
Description
An swipl executable consuming 100% of one CPU core remained running on each buildbot worker machine for days after the swi-prolog-devel port was recently updated to version 8.1.22, until I noticed it just now and killed it.
I don't know if the same would happen for the swi-prolog @8.0.2 port.
Please ensure this is fixed so that our limited server resources are not wasted.
Change History (2)
comment:1 Changed 5 years ago by ryandesign (Ryan Carsten Schmidt)
comment:2 Changed 4 years ago by reneeotten (Renee Otten)
Ryan, I just updated/merged updates for both the swi-prolog and swi-prolog-devel ports and didn't check for tickets first... However, both ports build correctly on the buildbot workers as far as I can tell, so I don't expect any problems you noted in this ticket anymore. But perhaps you could confirm that there are indeed no stray processes running anymore on the buildbots and, if appropriately, close this ticket if all looks good?
It's probably related that the installation failed on all buildbot workers (here's the log from 10.15) when more than an hour elapsed without the installation doing anything. (Our buildbot is configured with this one-hour timeout to ensure that builds that get stuck don't take a build server out of service forever).