[SERVER-10199] buildlogger failure on buildbot Linux RHEL 64-bit Created: 13/Jul/13 Updated: 02/Oct/13 Resolved: 02/Oct/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Matt Kangas | Assignee: | Ernie Hershey |
| Resolution: | Done | Votes: | 0 |
| Labels: | buildbot | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
buildbot Linux RHEL 64-bit Build #1377 |
||
| Operating System: | ALL |
| Participants: |
| Description |
|
If we verify the failure is due to buildbot, bump Fix Version to 2.5.2. Edit: http://buildbot.mongodb.org/builders/Linux%20RHEL%2064-bit/builds/1377/steps/test_9/logs/stdio (was http://buildbot.mongodb.org/builders/Linux%20RHEL%2064-bit/builds/1377/steps/test_8/logs/stdio) What's peculiar here is, apparently, there were no test failures, only buildlogger URLErrors. stdio (1377/steps/test_8/logs/stdio) ends with:
Yet Buildbot still considered this build as failed. |
| Comments |
| Comment by Tad Marshall [ 25/Jul/13 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||
|
The output of the last test looks pretty gnarly too ... that's a lot of log spam ...
| |||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Matt Kangas [ 25/Jul/13 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Again on buildslave bs-rhel-57-64-1 Linux RHEL 64-bit Build #1418 July 25 | |||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Matt Kangas [ 18/Jul/13 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||
|
More buildlogger errors on buildslave bs-rhel-57-64-1 Linux RHEL 64-bit Build #1384 July 18 http://buildbot.mongodb.org/builders/Linux%20RHEL%2064-bit/builds/1384/steps/test_11/logs/stdio | |||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Ernie Hershey [ 15/Jul/13 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||
|
This machine has been up for 339 days. It needs a reboot and should maybe even be rebuilt. I'll try to reproduce the buildlogger errors. I see some builds have succeeded since the errors happened, but the box is really slow. I bet I can reproduce the error behavior. | |||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Matt Kangas [ 14/Jul/13 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||
|
milkie Doh! You're right, and this is another demonstration that peer review is a good thing. I will retitle this ticket as just "buildlogger failed". test_9 here is first time I've seen test output go to stdio rather than buildlogger. | |||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Eric Milkie [ 14/Jul/13 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||
|
matt.kangas@10gen.com I think you misclicked; the failing test suite is test_9 but your link above is test_8. This is a duplicate of the chaining.js test failure. |