make check fails with "A test appears to be hung. There has been no output for 600 seconds."
Bug #629746 reported by
Māris Fogels
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Won't Fix
|
High
|
Māris Fogels | ||
Bug Description
See https:/
"I am unable to do a full test suite run locally. I tried twice.
I am testing lp:~abentley/launchpad/permit-commands and I'll test
another branch to be sure, but it doesn't look like something I changed
caused this.
"
Revision history for this message
| Māris Fogels (mars) wrote | #1 |
| Changed in launchpad-foundations: | |
| status: | Triaged → Won't Fix |
Revision history for this message
| Martin Pool (mbp) wrote | #2 |
Revision history for this message
| Robert Collins (lifeless) wrote Re: [Bug 629746] Re: make check fails with "A test appears to be hung. There has been no output for 600 seconds." | #3 |
To post a comment you must log in.
It turns out that 'make check' is a target intended for automated test runs. Developers likely want to run the much less troublesome 'bin/test' command. I am marking this as Won't Fix for now.
The one think bin/test does not do is start xvfb-run to hide the windmill test suite browser windows, but that is easy for developers to do on the command-line.