Opened 11 years ago

Last modified 11 years ago

#38662 new enhancement

RFE: Replace "command execution failed" with a more informative error message

Reported by: cooljeanius (Eric Gallager) Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: base Version: 2.1.3
Keywords: Cc:
Port:

Description

One thing I've noticed from looking at a bunch of trac tickets is that users will often report their errors as "command execution failed", when in reality, the log and debug output will show something more specific. It'd be useful to replace the "command execution failed" message with something more informative, so that maintainers don't have to go changing this in ticket titles all the time.

Change History (6)

comment:1 Changed 11 years ago by jmroot (Joshua Root)

What would you suggest? I doubt we can develop an AI that can automatically summarise the actual problem in the log.

comment:2 Changed 11 years ago by larryv (Lawrence Velázquez)

Maybe the error can mention the phase, at least? Although “build failed” is not really any better than “command execution failed”, as far as usefulness goes.

Last edited 11 years ago by larryv (Lawrence Velázquez) (previous) (diff)

comment:3 Changed 11 years ago by cooljeanius (Eric Gallager)

Or maybe it could mention what exactly the command was that failed. So instead of just "command execution failed" it could say something like "execution of "make" failed" or something...

comment:4 in reply to:  3 Changed 11 years ago by larryv (Lawrence Velázquez)

Replying to egall@…:

Or maybe it could mention what exactly the command was that failed. So instead of just "command execution failed" it could say something like "execution of "make" failed" or something...

How would we reliably extract the executable name from a given command string?

Honestly, we’re probably going to be editing the ticket anyway, so I’m not sure that this is worth putting effort into.

comment:5 Changed 11 years ago by neverpanic (Clemens Lang)

Well, it could just print the failed command completely. That would be a lot more specific, although the commands might actually get pretty long.

comment:6 Changed 11 years ago by cooljeanius (Eric Gallager)

for cross-referencing purposes, #39836 is similar

Note: See TracTickets for help on using tickets.