Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Print full error message if cargo fails #3140

Open
levBagryansky opened this issue Apr 24, 2024 · 1 comment · May be fixed by #3185
Open

Print full error message if cargo fails #3140

levBagryansky opened this issue Apr 24, 2024 · 1 comment · May be fixed by #3185

Comments

@levBagryansky
Copy link
Member

Now it prints just

[ERROR] Failed to build cargo project with dest = /private/var/folders/xj/f4s949893tq37zzw0pdmd68h0000gn/T/junit8772813024511140751/target/eo-test/Lib/native10
[ERROR] Non-zero exit code #101 of 'cargo'
Copy link

@levBagryansky thanks for the report, here is a feedback:

Problems

  • The bug report is missing important information: It doesn't specify the software version affected by the bug.
  • Steps to reproduce the bug are absent: The report doesn't provide the necessary steps to reproduce the bug, which are essential for developers to determine and rectify the problem.
  • Expected vs Actual Results are not stated: The report fails to mention the anticipated result compared to the actual occurrence.

Suggestions

  • Specify the Software Version: Always specify the version of the software where the bug occurred. This helps to identify if the bug is version-specific.
  • Include Steps to Reproduce: Always include the exact steps to reproduce the bug. This will enable the developers to see the bug in action, understand its context and ultimately to fix it.
  • State Expected vs Actual Result: Clearly state what the expected outcome should have been in contrast to the actual result. This helps the developers to understand the impact of the bug and what it is preventing the software from doing.
  • Use a Bug Report Template: Follow a structured template to ensure all important information is included. An example template could be:
Title: Incomplete Error Message When Cargo Fails to Build
Software Version: (Specify the software version)
Description: When trying to build cargo, the error message that is printed is incomplete.
Steps to Reproduce:
1. (Specify the first step)
2. (Specify the second step)
3. (Etc.)
Expected Result:
(Full error message is displayed allowing for easier troubleshooting)
Actual Result:
(Error message is incomplete, only displaying:

[ERROR] Failed to build cargo project with dest = /private/var/folders/xj/f4s949893tq37zzw0pdmd68h0000gn/T/junit8772813024511140751/target/eo-test/Lib/native10
[ERROR] Non-zero exit code #101 of 'cargo'

)

Please fix the bug report in order it to get resolved faster.
Analyzed with gpt-4

levBagryansky added a commit to levBagryansky/eo that referenced this issue May 12, 2024
@levBagryansky levBagryansky linked a pull request May 12, 2024 that will close this issue
levBagryansky added a commit to levBagryansky/eo that referenced this issue May 12, 2024
levBagryansky added a commit to levBagryansky/eo that referenced this issue May 12, 2024
levBagryansky added a commit to levBagryansky/eo that referenced this issue May 12, 2024
levBagryansky added a commit to levBagryansky/eo that referenced this issue May 13, 2024
levBagryansky added a commit to levBagryansky/eo that referenced this issue May 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant