Closed (won't fix)
Project:
Project issue file test
Version:
5.x-1.x-dev
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
31 Oct 2008 at 07:25 UTC
Updated:
15 Mar 2009 at 23:50 UTC
Jump to comment: Most recent file
Comments
Comment #1
catchWas about to post this, but found this one first:
This issue the links are fine:
http://drupal.org/node/298600
This one the html gets escaped:
http://drupal.org/node/299088
Comment #2
hunmonk commentedi don't experience this issue on my test install using the garland theme. what d.o specific setting would be doing this?
Comment #3
catchOn the two links above, both now appear fine as well, I've not seen the error crop up anywhere else recently either.
Comment #4
boombatower commentednoticed #2946: Login fails and no warning is issued if cookies are not enabled has issue
Comment #5
catchhttp://drupal.org/node/2946#comment-864187 looks fine to me?
Comment #6
boombatower commentedVery odd, it wasn't like that yesterday....this seems like these issues come and go...not sure if it is due to the results being re-reported and w/e code was faulty isn't behaving poorly.
Comment #7
alexanderpas commentedCritical as per:
http://drupal.org/node/329973
Comment #8
boombatower commentedJust as note:
#330521: Broken "Detailed results" link on comment.
#329730: Misformated test failure message for patch
Comment #9
boombatower commentedAs a note hunmonk, webchick, and I spent an hour or so messing/debugging/hacking/googling and got no where.
Comment #10
hunmonk commentedhere's a patch i applied to PIFT server on d.o to inspect the raw XML-RPC response from testing.drupal.org. hopefully this will help
Comment #11
damien tournoud commentedKilles was kind enough to dump a row of the pift_data table on d.o:
--> The issue appears to be on the testing.drupal.org side.
Comment #12
hunmonk commentedyes, we've known that the database entries were incomplete for awhile now. we've also determined that the raw xmlrpc we get back from testing.drupal.org always contains the escaped angle brackets -- so the current theory is that we're losing them in xmlrpcs.inc somewhere.
Comment #13
dave reidSubscribing. This has hit the majority of patches I've been working on.
Comment #14
hunmonk commentedupdate: chx and i ran some of the raw xml data through xmlrpcs.inc manually, and had zero problems. at this point i have no idea what else to check :|
Comment #15
alexanderpas commentedit seems like the
<and>are getting lost early in the process on t.d.o (or doesn't get added at all)someone needs to check exactly when that is happening (trace?)
Comment #16
hunmonk commented@alexanderpas: read #12
Comment #17
boombatower commentedUpdate: as of a while back this has been debugged by hunmonk, webchick, and with no conclusive results. (since we are getting more issues about this)
Comment #18
hunmonk commentedhere's an updated version of the hack i had on d.o to catch an XML-RPC response
Comment #19
boombatower commentedThis should no longer exist in 2.x due to a change in the way the link will be generated.