Opened 8 weeks ago

Last modified 7 weeks ago

#57405 assigned defect

atom @1.31.2 build failed on Mojave

Reported by: rlhamil Owned by: kurthindenburg (Kurt Hindenburg)
Priority: Normal Milestone:
Component: ports Version: 2.5.4
Keywords: mojave Cc: michaellass (Michael Lass)
Port: atom

Description

main.log attached

Attachments (3)

main.log-atom.txt (111.9 KB) - added by rlhamil 8 weeks ago.
main.log-atom-debug.txt (102.4 KB) - added by rlhamil 7 weeks ago.
2018-10-22T11_30_52_311Z-debug.log.txt (46.1 KB) - added by rlhamil 7 weeks ago.

Download all attachments as: .zip

Change History (9)

Changed 8 weeks ago by rlhamil

Attachment: main.log-atom.txt added

comment:1 Changed 8 weeks ago by ryandesign (Ryan Schmidt)

Owner: set to kurthindenburg
Status: newassigned

comment:2 Changed 8 weeks ago by michaellass (Michael Lass)

Cc: michaellass added

comment:3 Changed 7 weeks ago by michaellass (Michael Lass)

I cannot reproduce this issue on my side. The log looks to me like extracting a downloaded file does not work. Maybe there was a temporary issue with one of the download sources. Could you retry building atom after cleaning the build directory (sudo port clean atom)?

If the error is reproducible: Does the log file at /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_editors_atom/atom/work/.home/.npm/_logs/*-debug.log contain any useful information?

Changed 7 weeks ago by rlhamil

Attachment: main.log-atom-debug.txt added

Changed 7 weeks ago by rlhamil

comment:4 Changed 7 weeks ago by rlhamil

Cleaned, ran port -d install atom, attached main.log (debug version) and the file you mentioned. In the latter, it looks like it gave up, but I don't see that it's informative as to why.

Last edited 7 weeks ago by rlhamil (previous) (diff)

comment:5 in reply to:  4 Changed 7 weeks ago by michaellass (Michael Lass)

Replying to rlhamil:

In the latter, it looks like it gave up, but I don't see that it's informative as to why.

Indeed not very informative. Right now I have no idea what is going on here. You may try to build atom outside of macports as described here to see if it is an upstream issue or an issue with the Portfile. If it is upstream you may open an issue on github.

@kurthindenburg: Any other ideas? I'm not sure if this issue is Mojave-related as it does not occur on my system.

comment:6 Changed 7 weeks ago by rlhamil

Both by hand and via MacPorts, it took multiple tries to get it done, and didn't work at all at first. That could have been either a problem upstream, or with the network near my end - this seems to do a lot of downloading in the process of building, not just at the beginning. Even once it was working (and following the log file), it would seem to hang, but interrupting the build and restarting it made progress.

Very temperamental. Not sure how much of that is the downloads during build, and how much of that (seeming to stop making progress) might be race conditions or some other issue, whether platform specific or otherwise.

Can the build bots build this? Given how slow (as well as temperamental) the build is, it would help!

Note: See TracTickets for help on using tickets.