[#QB-2523] Improve the build overview page.

QuickBuild

Improve the build overview page.

Created: 26/Aug/15 09:18 AM Updated: 27/Aug/15 11:13 PM

Component/s:

None

Affects Version/s:

None

Fix Version/s:

None

Original Estimate:

Unknown

Remaining Estimate:

Unknown

Time Spent:

Unknown

File Attachments:

None

Image Attachments:

1. what-went-wrong.png
(1.37 Mb)

Description

« Hide

A common complaint I've had about using QB for Neovim is that it's really difficult to find out what went wrong on the build overview page. Our repository is being watched by 14,000+ people, and we have nearly 200 contributors. Most of them are not intimately familiar with the build systems, and so it's really important for them to be able to find out what went wrong and quickly from the build overview page. The net affect is that it can leave an overall poor impression on an otherwise good tool.

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

John Szakmeister [26/Aug/15 09:19 AM]

Here's a sample screen shot demonstrating the issue.

[ Permlink | « Hide ]

John Szakmeister [26/Aug/15 09:20 AM]

I've attached a screen shot demonstrating the problem. Hopefully it becomes clear at a glance that you really can't discern what happened that caused the issue. It leaves people frustrated. It would almost be better to link to the step status page from the pull request than the overview page (though I don't think that is an adequate solution).

[ Permlink | « Hide ]

John Szakmeister [26/Aug/15 09:22 AM]

I meant to add, that in the build in the screen shot failed because the functional tests timed out on all 6 builds being performed.

[ Permlink | « Hide ]

Robin Shen [27/Aug/15 12:40 AM]

It seems that the build failure is actually caused by "Failed to parse file" error. Is this the unit test error you are mentioning?

[ Permlink | « Hide ]

John Szakmeister [27/Aug/15 01:29 AM]

Yes. We launch Neovim in a special mode to run tests against it, but it had some issues starting up correctly. As a result, the step would time out, and the test results was just an empty file. But the real point was that it's hard to tell what actually happened from the build overview page. It's quite a lot of output, and most of the noise masks the real issue. Other failures look similarly bad.

[ Permlink | « Hide ]

Robin Shen [27/Aug/15 11:13 PM]

It would be hard to parse out and display the accurate build cause. Would it be clear if we remove various "composite step xxx failed due to unsatisified condition"? That will only leaves with the "Failed to parse file".