Closed (fixed)
Project:
DrupalCI: Test Runner
Component:
Artifacts and Output
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
27 Oct 2015 at 07:38 UTC
Updated:
20 Jan 2017 at 09:04 UTC
Jump to comment: Most recent
The rule name shows as cut off in the results.
| Comment | File | Size | Author |
|---|---|---|---|
| Capture.PNG | 10.56 KB | elachlan |
Comments
Comment #2
MixologicComment #3
jonathan1055 commentedYes, I have had this a few times and could not see any particular pattern. Is it worth linking the specific results here? Mine were fairly recent. I will get the links.
Comment #4
MixologicComment #5
jonathan1055 commentedI don't think I have seen this problem for a while. If I do I will link to the results.
Comment #6
elachlan commentedHere is an example
https://www.drupal.org/pift-ci-job/314967
Comment #7
jonathan1055 commentedHere is an example from today of a core patch
https://www.drupal.org/pift-ci-job/461995
Is it caused by the fact that the name should start with a backslash, but it is not properly escaped? ... that somehow it evaluates
\Dwhich does not get displayed?Comment #8
mile23Working on the core parts here: #2810083: Duplicate test results per fail/exception
Comment #9
MixologicAlso, in JunitXMLFormat.php there is :
These can probably be replaced with a preg replace.
Its currently expecting "Drupal\Tests\field_ui\FunctionalJavascript\EntityDisplayTest->testEntityView()"
But sometimes gets just "Drupal\Tests\field_ui\FunctionalJavascript\EntityDisplayTest" (which the causes the first character and last 2 chars to get cut off.)
Sometimes we get only the word 'Unknown' (Unknown becomes nkno because of these substrings).
so, better logic needed there.
Comment #10
elachlan commentedDo we do that change in #2810083: Duplicate test results per fail/exception or here?
Comment #12
MixologicWe change it here. I changed it, its on a branch. When we move it into dev, then production it'll be fixed for all.
Comment #13
mile23We can make a more isolated unit test of
generateJunitXml()once #2823816: Always use the container-injected build, modify BuildTaskInterface::run() and ::start() to not pass $build is in and clarifies which build object is in control.Comment #14
MixologicIm going to mark this as fixed, and open a follow up to add a test for the generated junit xml