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

Multiline error message is cut out from the output #105

Open
Skoti opened this issue Apr 21, 2023 · 14 comments
Open

Multiline error message is cut out from the output #105

Skoti opened this issue Apr 21, 2023 · 14 comments

Comments

@Skoti
Copy link

Skoti commented Apr 21, 2023

When an error message is multiline, like this:

/redacted/path/to/file.swift:31: error: -[redacted.package.testfile testRedactedName] : failed: caught error: "code: 1, Error: code: 1, FAILURE: Build failed with an exception.

* What went wrong:
Some problems were found with the
multiple lines here
BUILD FAILED in 1s"

then xcbeautify output only displays:

Redacted
    ✖ testRedactedName, failed: caught error: "code: 1, Error: code: 1, FAILURE: Build failed with an exception.
@nunogoncalves
Copy link

Yes! I was just noticing this too!

@github-actions
Copy link

github-actions bot commented Jul 4, 2023

Hola 👋,

We want to inform you that the issue has been marked as stale. This means that there hasn't been any activity or updates on it for quite some time, and it's possible that it may no longer be relevant or actionable.
If you still believe that this issue is valid and requires attention, please provide an update or any additional information that can help us address it. Otherwise, we may consider closing it in the near future.
Thank you for your understanding.

@github-actions github-actions bot added the stale label Jul 4, 2023
@Skoti
Copy link
Author

Skoti commented Jul 4, 2023

It is still relevant.

@nunogoncalves
Copy link

Yes. Still relevant! :(

@farshadtx
Copy link

+1

@aetherealtech
Copy link

This is a problem for us too. We use tools that emit multiline test failure messages. We currently have to download raw logs to view these messages.

@github-actions
Copy link

Hola 👋,

We want to inform you that the issue has been marked as stale. This means that there hasn't been any activity or updates on it for quite some time, and it's possible that it may no longer be relevant or actionable.
If you still believe that this issue is valid and requires attention, please provide an update or any additional information that can help us address it. Otherwise, we may consider closing it in the near future.
Thank you for your understanding.

@github-actions github-actions bot added the stale label Aug 21, 2023
@nunogoncalves
Copy link

Still relevant.

@github-actions github-actions bot removed the stale label Aug 22, 2023
@github-actions
Copy link

Hola 👋,

We want to inform you that the issue has been marked as stale. This means that there hasn't been any activity or updates on it for quite some time, and it's possible that it may no longer be relevant or actionable.
If you still believe that this issue is valid and requires attention, please provide an update or any additional information that can help us address it. Otherwise, we may consider closing it in the near future.
Thank you for your understanding.

@github-actions github-actions bot added stale and removed stale labels Sep 21, 2023
@github-actions
Copy link

Hola 👋,

We want to inform you that the issue has been marked as stale. This means that there hasn't been any activity or updates on it for quite some time, and it's possible that it may no longer be relevant or actionable.
If you still believe that this issue is valid and requires attention, please provide an update or any additional information that can help us address it. Otherwise, we may consider closing it in the near future.
Thank you for your understanding.

Copy link

Hola 👋,

We want to inform you that the issue has been marked as stale. This means that there hasn't been any activity or updates on it for quite some time, and it's possible that it may no longer be relevant or actionable.
If you still believe that this issue is valid and requires attention, please provide an update or any additional information that can help us address it. Otherwise, we may consider closing it in the near future.
Thank you for your understanding.

@github-actions github-actions bot added stale and removed stale labels Nov 22, 2023
Copy link

Hola 👋,

We want to inform you that the issue has been marked as stale. This means that there hasn't been any activity or updates on it for quite some time, and it's possible that it may no longer be relevant or actionable.
If you still believe that this issue is valid and requires attention, please provide an update or any additional information that can help us address it. Otherwise, we may consider closing it in the near future.
Thank you for your understanding.

@github-actions github-actions bot added stale and removed stale labels Dec 24, 2023
Copy link

Hola 👋,

We want to inform you that the issue has been marked as stale. This means that there hasn't been any activity or updates on it for quite some time, and it's possible that it may no longer be relevant or actionable.
If you still believe that this issue is valid and requires attention, please provide an update or any additional information that can help us address it. Otherwise, we may consider closing it in the near future.
Thank you for your understanding.

@nunogoncalves
Copy link

Still relevant

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

No branches or pull requests

5 participants