Opened 5 years ago

Closed 5 years ago

#59654 closed defect (invalid)

"[property value too long]" is included in portlist

Reported by: jmroot (Joshua Root) Owned by: admin@…
Priority: Low Milestone:
Component: buildbot/mpbb Version:
Keywords: Cc:
Port:

Description

Example: https://build.macports.org/builders/ports-10.8_x86_64-watcher/builds/1620

Notice [property, value, too and long] are in the portlist. The string seems to have been split on whitespace and then inserted into a set, resulting in the random order.

Fortunately it doesn't seem to cause any problems beyond mpbb list-subports complaining that ports by those names don't exist in the index.

Change History (2)

comment:1 Changed 5 years ago by ryandesign (Ryan Carsten Schmidt)

I've seen this [property value too long] before but I didn't think anything of it; I thought it was just a display issue, as in too long to display on the web page. But apparently it's a deeper problem than that. Does that mean that the full list of ports that I submitted to be built there didn't actually get built?

comment:2 Changed 5 years ago by ryandesign (Ryan Carsten Schmidt)

Resolution: invalid
Status: newclosed

No, it looks complete.

Instead, what probably happened is that I inadvertently submitted a list of ports that included the string [property value too long]. This build was a rescheduling of hundreds of builds that had failed on this builder because its disk was full. Some of the builds that failed were forced builds, so I could not just go by the list of files modified by the commits. So instead I built the port list for this build by downloading the html for each failed build and parsing out its fullportlist. I did notice that one of the builds had too many ports to list, and said [property value too long], but that this build made a change that didn't require a rebuild, so I had ignored it.

Note: See TracTickets for help on using tickets.