Skip to content

Different log output for tkn p log and tkn pr log #2223

@ctron

Description

@ctron

Versions and Operating System

  • Kubernetes version:

    Output of kubectl version:

    Client Version: v1.28.2
    Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
    Server Version: v1.25.11+1485cc9
    WARNING: version difference between client (1.28) and server (1.25) exceeds the supported minor version skew of +/-1
    
  • Tekton Pipeline version:

    Output of tkn version or kubectl get pods -n tekton-pipelines -l app=tekton-pipelines-controller -o=jsonpath='{.items[0].metadata.labels.version}'

    Client version: 0.34.0
    Chains version: v0.17.1
    Pipeline version: v0.50.3
    Triggers version: v0.25.2
    Operator version: v0.68.1
    
  • Operating System:

    Fedora release 39 (Thirty Nine)
    

Expected Behavior

Running tkn p log and tkn pr log gives a different representation. I would expect them to be the same.

Actual Behavior

image

Steps to Reproduce the Problem

  1. run tkn p log
  2. run tkn pr log
  3. compare

Additional Info

Metadata

Metadata

Assignees

Labels

good first issueDenotes an issue ready for a new contributor, according to the "help wanted" guidelines.kind/bugCategorizes issue or PR as related to a bug.

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions