The i386 build just hung in nbctfmerge for a third time. I have now disabled the i386 builds on babylon5 so that the other architectures can continue to be tested (unless the bug turns out to affect them, too). -- Andreas Gustafsson, [email protected]
- Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
- Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
- Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
- Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
- Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
- Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
- Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
- Re: Automated report: NetBSD-current/i386 build f... Andreas Gustafsson
- Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
- Re: Automated report: NetBSD-current/i386 build f... Andreas Gustafsson
- Re: Automated report: NetBSD-current/i386 build f... Andreas Gustafsson
- Re: Automated report: NetBSD-current/i386 build f... Andreas Gustafsson
- Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
- Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
- Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
- Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
- Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
- Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
- Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
- Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
- Automated report: NetBSD-current/i386 build failure NetBSD Test Fixture
