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

Unspecific Errors from Pipeline #1178

Closed
gmischler opened this issue May 20, 2024 · 3 comments
Closed

Unspecific Errors from Pipeline #1178

gmischler opened this issue May 20, 2024 · 3 comments
Assignees

Comments

@gmischler
Copy link
Collaborator

When something fails in the checking pipeline for a PR, then recently the error message from the respective subprocess isn't displayed anymore. All we get to see is eg. this:
grafik
Where currently there is only a lonely "Error:" now, there used to be the full stderr output of the failing check.
What has changed here?
Is this a deliberate change?
Can it be fixed please?

As a reviewer, the current lack of detail information makes it rather hard to give useful advice. Unfortunately I'm not familiar enough with the pipeline mechanics to fix it myself...

@gmischler gmischler added the bug label May 20, 2024
@Lucas-C
Copy link
Member

Lucas-C commented May 23, 2024

Hi @gmischler 🙂
Thank you for reporting this!

I'm sorry but I do not reproduced your problem... 😞

The last failing GitHub Actions execution is this one: https://github.com/py-pdf/fpdf2/actions/runs/9155251026/job/25201525486

The failure gets displayed this way in my Firefox browser on Windows:
Capture d'écran 2024-05-23 131544

Do you see the same thing?

Could you please provide a link to job where the problem occurs?

@gmischler
Copy link
Collaborator Author

My screenshot was from #1176, which shows a full error message now.

If you didn't change anything in the pipeline, then I guess it was a hickup on githubs side, which is fixed now.

@Lucas-C
Copy link
Member

Lucas-C commented May 23, 2024

Yes, I think that you are right!

In my experience, sometimes reloading the jobs log page can help to resolve some display issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants