© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
7020100
(Get the code!)
The 4 piuparts errors have cleared.
The remaining 3 failures are all on armhf, and while the logs aren't detailed I get the impression the test client isn't connecting with the apache2 server for performing the tests. So it seems like some irregularity in how apache2 runs on armhf.
Other than disabling the test or just keep retriggering, I think the right next action would be to enable more logging output such as capturing the access.log, error.log, journalctl, and the apache2 service status. Hopefully that captures some further info that might clue us in on what's going on.
If someone has access to armhf vm's similar to the autopkgtest environment, it might be worth trying out installing these components and see if apache2 works.