You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When one of the buildbot steps fails, the only thing we see in the logs is the command itself, which isn't very helpful in diagnosing the problem for packagers to solve.
But the steps have names associated, which should be printed when the step fails. Then, the names could be expanded so they hint at the exact failure cause. Eg.
Check for right id in AppStream xml could be Check that desktop file id matches Flatpak ID org.gnome.Test
The text was updated successfully, but these errors were encountered:
When one of the buildbot steps fails, the only thing we see in the logs is the command itself, which isn't very helpful in diagnosing the problem for packagers to solve.
But the
steps
have names associated, which should be printed when the step fails. Then, the names could be expanded so they hint at the exact failure cause. Eg.Check for right id in AppStream xml
could beCheck that desktop file id matches Flatpak ID org.gnome.Test
The text was updated successfully, but these errors were encountered: