Closed Bug 616161 Opened 14 years ago Closed 14 years ago

test_clobberer.py fails in preproduction

Categories

(Release Engineering :: General, defect, P2)

Product:
Release Engineering
Component:
General
Platform:
x86
Linux
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: rail, Assigned: rail)

Details

python test_clobberer.py http://preproduction-master.build.mozilla.org/~cltbld/index.php /home/cltbld/public_html/db/clobberer.db
 in dir /builds/buildbot/preproduction/slave/test-masters/tools/clobberer

...

F...............
======================================================================
FAIL: Test that clobbers on release builders with the
----------------------------------------------------------------------
Traceback (most recent call last):
  File "test_clobberer.py", line 372, in testReleaseClobberPrefixBuilder
    self.assert_('release-mozilla-central-linux_build' in data, data)
AssertionError: <html>
<head>
<title>Mozilla Buildbot Clobberer</title>
<link rel="stylesheet" href="clobberer.css" type="text/css" />
<script src="jquery.min.js" language="javascript"></script>
<script language="javascript">
function toggleall(node, klass)
{
  if (klass) {
    $("." + klass).attr("checked", node.checked);
  }
  var node_classes = $(node).attr("class").split(" ");
  if (!node.checked) {
    // If we just unchecked a node, then uncheck the parents too
    for (var i = 0; i < node_classes.length; ++i) {
      if (node_classes[i]) {
        $("#" + node_classes[i]).attr("checked", false);
      }
    }
  } else {
    // If we just checked a node, then possibly check the parents if all
    // children are checked
    var done = false;
    while (!done) {
      done = true;
      for (var i = 0; i < node_classes.length; ++i) {
        if (node_classes[i]) {
          // If none of this class is unchecked, then we can check the parent
          if ($("." + node_classes[i] + ":not(:checked)").length == 0) {
            var p = $("#" + node_classes[i]);
            if (p && !p.attr("checked")) {
              p.attr("checked", true);
              // Loop through again if we just set our parent to checked
              done = false;
            }
          }
        }
      }
    }
  }
}
</script>
</head>
<body>
<p>This page is used for clobbering buildbot-based builds.</p>
<p>Please read
<a href="https://wiki.mozilla.org/Build:ClobberingATinderbox">Build:ClobberingATinderbox</a>
and/or <a href="https://wiki.mozilla.org/Clobbering_the_Tree">Clobbering the Tree</a>
for more information about what this page is for, and how to use it.</p>

<form method="POST">
<table border="1" cellspacing="0" cellpadding="1">
 <thead>
  <tr><td>Branch</td><td>Builder Name</td><td>Slaves</td><td>Last clobbered</td></tr>
 </thead>
 <tbody>
 </tbody>
</table>
<input type="hidden" name="form_submitted" value="true">
<input type="submit" value="Clobber now">
</form>
</body>
</html>

----------------------------------------------------------------------
Ran 16 tests in 13.680s

FAILED (failures=1)
Syed - can you look at this? The failure is on the test you added in https://bug605267.bugzilla.mozilla.org/attachment.cgi?id=487516
Assignee: nobody → salbiz
Status: NEW → ASSIGNED
Priority: -- → P3
Looks like this is due to the REMOTE_USER server variable not being set, so isSpecial comes out false. I can't find a way to set this via the test harness, so it may be faster to set up a preproduction account that is allowed to see release clobbers
Assignee: salbiz → rail
Priority: P3 → P2
$ cat /home/cltbld/public_html/.htaccess 
SetEnv REMOTE_USER armenzg@m.c

(Sorry, Armen, you are the first in the list :) ).


snip from /etc/httpd/conf/httpd.conf:
====================================
<Directory /home/*/public_html>
    AllowOverride All
<Directory>
====================================

I also removed flunkOnFailure=False in http://hg.mozilla.org/build/preproduction/rev/6e5dc6cb7b13
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.