GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — JUnitReport system-out tag without CDATA · Issue #1084 · utPLSQL/utPLSQL

JUnitReport system-out tag without CDATA #1084

New issue
Copy link
New issue
Copy link
Closed
#1085
Closed
JUnitReport system-out tag without CDATA#1084
#1085
Copy link
Labels
bug
Milestone
v3.1.11

Description

@harmonicaCz
harmonicaCz
opened on Jun 26, 2020
Issue body actions

Describe the bug
Hello,
I try to updated to the new version 3.1.10 (from 3.1.6) and for junit_report was removed CDATA(start, end) tag cover for tag in xml. Is there any reason for it or it`s a bug? Since we used in system logs lot of the special chars (like <,>, -...) then generated junit_report.xml in jenkins is unable to parse it.
Second question: is there any possibility to disable the system-out for tests?

Provide version info
Information about utPLSQL and Database version,

Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production

Information about client software
I tested for TOAD and also through the utplsql-cli (3.1.7)
UT v3.1.6.2735 (working)
UT v3.1.10 (not work)

Expected behavior
Jenkins could parse xml output file for junit report.
So the system-out has to be like this:

Example code

2020-06-26 12:28:27.922|8|gloTest2.startWatchingQueue ||Attached to TCQ_SAP_S. Last message ID: 150654, last IPC message ID: 21928443 2020-06-26 12:28:27.923|8|tstPESxADJArbPTG.L_createS35T0C02 ||-> create telegram S35T0C02... 2020-06-26 12:28:27.924|8|ADJArbPTG.processS35T0C02 ||-> 2020-06-26 12:28:27.924|8|ADJArbPTG.processS35T0C02 ||FOLGEST = 20190002 2020-06-26 12:28:27.925|8|kmp***ADJArbPTG.processS35T0C02 ||MAT 18100102[1151257] 2020-06-26 12:28:27.926|8|kmp***ADJArbPTG.L_moveMaterial ||Located at HBK RPL[1, 0727, 1] UOP[2, 1, M] meID: 1151257 2020-06-26 12:28:27.926|8|entLagerPTG.getLager4SAP ||-> SAP LagerTyp / LagerPlatz: / 0727 2020-06-26 12:28:27.972|8|entLagerPTG.getLager4SAP ||<- HBK

Additional context
I tested from 3.1.6 to 3.1.10 and since 3.1.7 the CDATA tag => are missing.

Activity

  1. jgebal
    added
    bug
    on Jun 28, 2020
  2. jgebal commented on Jun 28, 2020

    @jgebal
    jgebal
    on Jun 28, 2020
    Member
    More actions

    Thanks for reporting this issue @harmonicaCz
    It is clearly a regression issue.

    I'm looking at fixing it now.

  3. jgebal
    added a commit that references this issue on Jun 28, 2020

    Fixed CDATA tagging in JUnit reporter

    This issue will close once commit cd7d738 is merged into the 'develop' branch.
    cd7d738
  4. jgebal
    added this to the 3.1.11 milestone on Jun 28, 2020
  5. jgebal
    closed this as completedin #1085on Jul 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bug

    Type

    No type

    Projects

    No projects

      Milestone

      • v3.1.11

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.