Closed (fixed)
Project:
Drupal.org Testbots
Component:
unexplained test failure
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
21 Nov 2011 at 00:41 UTC
Updated:
9 Dec 2011 at 18:20 UTC
Jump to comment: Most recent file

Comments
Comment #1
rfayYour test assumes that clean_urls are on. They're not on the testbot (and are not on in Drupal by default; that's why).
There are two key differences between most people's environments and the testbot:
1. No clean urls by default (although your test could turn this on)
2. It runs in a subdirectory
So a typical URL would be http://drupaltestbot654.osuosl.test/checkout/?q=comment/...
Comment #2
rfayI should mention here that you can easily run your own testbot, in a virtual machine, on an VM on the internet, or etc. It's linked to at the bottom of http://drupal.org/project/testbot
Also, I added this question to the FAQ there.
Comment #3
salvisOh, wow — thank you!
It has been years since I got in contact with 'dirty' urls... :-)
And thanks for the additional information, too.
Comment #4
salviswas the key to getting this to pass.
No sloppy programming in the test code either!
I'm just so thrilled to have recurring tests in place now:
Thank you for that!
Comment #5
rfayCongratulations!
Just FYI though... they're not recurring at this point, although I hope they will be. Currently tests get executed when you do a commit or post a patch.
20K assertions in D6 and 10K in D7? You're really working that testbot hard!
Comment #6
salvisYes, I know, and I'm somewhat uneasy that this might get me into trouble...
The problem with Forum Access is that there are many different combinations of permissions and grants that result in all sorts of interactions. If you really want to nail this down, you have to test a large number of these combinations or you risk missing one that could open up unwanted access.
The testbot is amazingly fast though!
Comment #7
jthorson commentedActually, Randy, they are ... I turned them on for Forum Access earlier this week. ;)
Comment #8
rfay@jthorson I meant that they don't happen on a repeating basis without something triggering them. Unless you've implemented a feature I've been hoping for.
Examples D8 has already broken several times due to core shifts, but we don't find out until a commit...
Comment #9
salvisD7 core shouldn't change so much as to regularly break contribs anymore, but the modules that want to track the bleeding edge D8 would benefit greatly from periodic retests, maybe in idle times of the bots, if these exist.
Comment #10
salvisRe. #1, differences between most people's environments and the testbot:
Everything is green, but we're seeing different pass counts for Forum Access D6 on qa.d.o and when we run the tests locally. Initially, we had the verbose setting on locally, and this resulted in about 10% more passes, because every verbose message increases the pass count by 1.
After turning verbose off, we're seeing about 3% less passes locally (and on the local testbot that daffie set up) than on qa.d.o. Does qa.d.o run some additional tests?
I've tried turning clean URLs off locally, but this didn't make any difference. I've also looked at the D7 version, and got mixed results, see #762270-37: WANTED: SimpleTests for Forum Access.
Any idea what could be causing the different pass counts?
Comment #11
rfayFor a while on D6 some core tests were being run, but I think that's been fixed.
I think you can look at the summary and see what tests are being run, although that doesn't account for all the assertions counted.
Comment #12
salvisYes, these are still running...
... but the way this is presented I don't think their counts are added to the FA counts.
BTW, in the log the tests show up in a systematic way, but further up on http://qa.drupal.org/pifr/test/193549 they look less orderly: