View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0004036Compliance Test Tool (CTT) Unified Architecture3 - Feature Requestpublic2017-10-26 13:102019-08-07 11:46
ReporterFrançois Vandewalle Assigned ToAlexander Allmendinger  
PrioritynormalSeveritycrashReproducibilityalways
Status closedResolutionfixed 
Target Version1.03Fixed in Version1.03.341.381 
Summary0004036: CTT crashes when performing "save all"; test history gets lost
Description

I have a CTT project with 135 historical runs.
I perform a new run and it runs well.
Then I click the "save all" icon and the CTT crashes.

After this, the test history is lost.
The file {project_name}_results.xml is still there but its size is zero.

Steps To Reproduce

I am joining a zip file with my CTT project.
With it, I was able to reproduce the issue 100%

Additional Information

I am using the current CTT release candidate (1.3.340.358)

When I remove some historical runs "by hand" from the results file (ex: "Debug Run1" to "Debug Run50"), then:

  • I can make tests and save like before I experienced the crash
  • however, the new runs get names that were already used and not deleted (ex: "Debug Run88")
TagsNo tags attached.
Files Affected

Relationships

has duplicate 0004035 closedPaul Hunkar CTT crashes when performing "save all"; test history gets lost 

Activities

François Vandewalle

2017-10-26 13:54

reporter   ~0008604

Last edited: 2017-10-26 13:55

I am having a problem uploading the file with my CTT project (Mantis application error 401).
Also this issue is duplicate.

I have sent a mail to mantis@opcfoundation.org but is came back.
Please suggest another medium for transfer (mail ?).

François Vandewalle

Paul Hunkar

2017-11-02 14:40

administrator   ~0008636

You can email it to compliance@opcfoundation.org or email a link to where it is posted.

Paul Hunkar

2018-04-05 15:16

administrator   ~0008996

This issue is a CTT infrastructure issue, we will add a limit to the CTT to store only 100 or some configurable amount of history and warna user if they are exceeding. Possible behaviour would be to drop the oldest and not exceed the maximum.

Alexander Allmendinger

2018-10-18 09:12

developer   ~0009484

This was no fixed limit but a problem with the number of XMLElements in the file which is depending on the number of scripts, warning and errors within the project. Nevertheless after changing to a XmlStream we are good and this shouldn't happen any more.

Paul Hunkar

2019-08-07 11:46

administrator   ~0010702

reviewed in CMP call 8/1/2019

Issue History

Date Modified Username Field Change
2017-10-26 13:10 François Vandewalle New Issue
2017-10-26 13:54 François Vandewalle Note Added: 0008604
2017-10-26 13:54 François Vandewalle Note Edited: 0008604
2017-10-26 13:55 François Vandewalle Note Edited: 0008604
2017-10-26 13:55 François Vandewalle Note Edited: 0008604
2017-11-02 14:39 Paul Hunkar Target Version => 1.04
2017-11-02 14:40 Paul Hunkar Note Added: 0008636
2017-11-02 14:42 Paul Hunkar Relationship added has duplicate 0004035
2018-04-05 15:16 Paul Hunkar Note Added: 0008996
2018-04-05 15:16 Paul Hunkar Assigned To => Paul Hunkar
2018-04-05 15:16 Paul Hunkar Status new => acknowledged
2018-04-05 15:17 Paul Hunkar Category General Problem => Feature Request
2018-07-31 17:30 Paul Hunkar Assigned To Paul Hunkar => Alexander Allmendinger
2018-07-31 17:30 Paul Hunkar Status acknowledged => assigned
2018-10-18 09:12 Alexander Allmendinger Note Added: 0009484
2018-10-18 09:12 Alexander Allmendinger Status assigned => resolved
2018-10-18 09:12 Alexander Allmendinger Fixed in Version => 1.03.341.381
2018-10-18 09:12 Alexander Allmendinger Resolution open => fixed
2019-01-28 14:14 Paul Hunkar Category Feature Request => 3 - Feature Request
2019-08-07 11:46 Paul Hunkar Target Version 1.04 => 1.03
2019-08-07 11:46 Paul Hunkar Status resolved => closed
2019-08-07 11:46 Paul Hunkar Note Added: 0010702