The results get stored correctly when testing locally, but they do not seem to be associated in db properly on temp master. Assuming the db issue is fixed I would bet the interface works fine.

For example: http://drupaltesting.deekayen.net/pifr/test/5

CommentFileSizeAuthor
#2 542268-assertion-detail.patch2.77 KBboombatower

Comments

boombatower’s picture

boombatower commented
Assigned: Unassigned » boombatower

Running the following query I see a large number of orphaned rows:

SELECT result_detail_id, status, message as message, message_group, function, line, file
FROM pifr_result_detail_assertion
WHERE result_detail_assertion_id NOT IN (
  SELECT a.result_detail_assertion_id
  FROM pifr_result_detail_assertion a
  JOIN pifr_result_detail d
    ON d.result_detail_id = a.result_detail_id
);

and using this I can see that no detail rows match the test that had fails, so this is definitely a data problem.

SELECT result_detail_id FROM pifr_result_detail WHERE result_id = (SELECT result_id FROM pifr_result WHERE test_id = 5 AND fail > 0) AND fail > 0;
boombatower’s picture

boombatower commented
StatusFileSize
new 542268-assertion-detail.patch2.77 KB

Debug patch placed on temp master that will dumb things to http://drupaltesting.deekayen.net/result.txt.

boombatower’s picture

boombatower commented
Status: Active » Fixed

Issue no longer seems to exist.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.