Opened 13 months ago
Closed 13 months ago
#68408 closed defect (fixed)
CI doesn't build ports in dependency order
Reported by: | barracuda156 | Owned by: | jmroot (Joshua Root) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | buildbot/mpbb | Version: | 2.8.1 |
Keywords: | Cc: | ryandesign (Ryan Carsten Schmidt), mascguy (Christopher Nielsen), cjones051073 (Chris Jones) | |
Port: |
Description
Either this or neighboring ones. We got all sorts of random failures for existing ports which built fine earlier and still build fine locally (not just for me, but for others too).
So far it is either alleged dependency cycle (which may involve test dependencies which are now, apparently, confused for build/lib dependencies) or activation failure.
Activating all dependencies... invalid command name "" while executing "$workername eval {validate_macportsuser}" (procedure "mportexec" line 5) invoked from within "mportexec $ditem activate" Error: Activate failed: invalid command name "" Activation of dependency 'gcc12-libcxx' with variants '+clang14' failed, aborting. Processing dependencies for 'R-ic.infer' failed, aborting.
Error: The following dependencies were not installed because all of them have unmet dependencies (likely due to a dependency cycle): libiconv Build of dependency 'libtextstyle' with variants '' failed, aborting.
Multiple examples here: https://github.com/macports/macports-ports/pull/20736 (where ports which are known to build fine, now failed on CI) Likely related too: https://github.com/macports/macports-ports/pull/20702 (this one involves changes to R PG, so may or may not be caused by mpbb, but I think it is)
Change History (4)
comment:1 Changed 13 months ago by barracuda156
comment:2 Changed 13 months ago by cjones051073 (Chris Jones)
Cc: | cjones051073 added |
---|
comment:3 Changed 13 months ago by jmroot (Joshua Root)
Summary: | Latest commits to mpbb have broken CI → CI doesn't build ports in dependency order |
---|
While there was an issue with mpbb, it only affected what is supposed to be a very rare case: when a dependency of the port being built has not itself been built yet. It only caused noticeable problems because the CI script appears to be simply building changed ports in the order they appear in the git diff, rather than in dependency order.
comment:4 Changed 13 months ago by jmroot (Joshua Root)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
From another PR:
Needless to say, everything worked fine earlier with all these.