Patches I file on an issue get marked as new but don't get added to the testbot queue.
Issue #2456043: Make exposed date filter operators terminology friendly to non-technical website visitors (D7):
1. I filed the patch in comment #4.
2. The patch failed.
3. I filed the patch in comment #7.
4. The patch failed because I was pointing to the current released branch.
5. I corrected the module version to the dev branch - see comment #9.
6. I clicked Retest in comment #7 - see comment #10.
7. The test request was sent.
8. The request never landed on the testbot queue.
9. I did various things to try to get the testbot to run, all to no avail: Comment #12 - set to needs work
10. Comment #13 - set to needs review
11. Comment #14 - set to needs work
12. Comment #15 - uploaded same patch with new name; test request sent but not added to queue
13. Comment #17 - uploaded same patch with new name; test request sent but not added to queue
14. Comment #18 - uploaded same patch with new name; test request sent but not added to queue
15. Comment #19 - set to needs work
16. Per Mixologic's suggestion on IRC, got the patch to apply locally first, then uploaded same patch with new name and set to needs review; test request sent but not added to queue
Comments
Comment #1
charles belovComment #2
charles belovHmm, while I was typing this, the test ran (sort of, got no results, but that's a different issue). It's still a problem if I've uploaded patches for testing and they don't run, even if running them would lead to a failure to apply. The patches in #4 was completely invalid and the bot still tried to apply it and gave a useful error report.
Comment #3
MixologicYes, that was me manually forcing the test to re-run. Even then Im seeing strange things. This is what is in the log:
Comment #4
MixologicThis is an issue with core's run_tests.sh that is breaking all patches to views.
Comment #5
MixologicThis was also fixed in drupalci