some testbox errors aren't being reported with stacktraces

Description

for some reason, some test failures aren’t having their errors and stacktraces printed out

works fine in Lucee 5.3, only 6.0 build was affected

Environment

None

Activity

Show:

Michael Offner 9 January 2023 at 15:27

reopen or new ticket? please do whatever necessary.

Zac Spitzer 23 July 2022 at 18:43

it’s better, but sometimes errors are being reported twice

remember that -DtestDebug=”true” print’s out full stracktraces

Zac Spitzer 16 July 2022 at 11:18

took some digging, but it turns out the specStats in the bundle results are both in a top level key and nested in under suiteStats[1].specStats

   { "startTime": 1657968673242, "totalPass": 6, "totalDuration": 390, "totalSkipped": 0, "totalFail": 0, "totalSpecs": 0, "bundleID": "5635269E500D51BB881E71819677371B", "status": "Error", "parentID": "", "specStats": [], "endTime": 1657968673632, "totalError": 2, "name": "Test suite for cftimeout Tag", "id": "5EE26A43CE0D03E3A82C85F3244613F4", "suiteStats": [ { "startTime": 1657968673244, "totalPass": 6, "totalDuration": 388, "totalSkipped": 0, "totalFail": 0, "totalSpecs": 8, "bundleID": "5635269E500D51BB881E71819677371B", "status": "Error", "parentID": "5EE26A43CE0D03E3A82C85F3244613F4", "specStats": [ { "error": {},

https://github.com/lucee/Lucee/pull/1701

Fixed

Details

Assignee

Reporter

Priority

Fix versions

New Issue warning screen

Before you create a new Issue, please post to the mailing list first https://dev.lucee.org

Once the issue has been verified, one of the Lucee team will ask you to file an issue

Sprint

Affects versions

Created 16 July 2022 at 11:09
Updated 9 January 2023 at 16:48
Resolved 9 January 2023 at 16:48

Flag notifications