Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Test cases TestWriteToWorkingDir and TestExtractSecretsToFile_Err are failing in pp64 architecture #2189

Open
jnanaj opened this issue Mar 8, 2023 · 0 comments
Labels
bug Something isn't working needs-triage New issues, in need of classification

Comments

@jnanaj
Copy link

jnanaj commented Mar 8, 2023

What happened?

When we run make test in pp64 architecture, below 2 test cases are failing and these two test cases contain a below comment saying these are OS dependent.

Failing test cases:

  1. TestWriteToWorkingDir
  2. TestExtractSecretsToFile_Err

Comment:

// Avoid assertions on OS-dependent error messages which may differ between OSes.

Console output for the testcases

=== RUN   TestWriteToWorkingDir
    elasticsearch_secrets_test.go:172:
                Error Trace:    /home/centos/Bhimrao/jaeger-operator/pkg/storage/elasticsearch_secrets_test.go:172
                Error:          Should be true
                Test:           TestWriteToWorkingDir
    elasticsearch_secrets_test.go:172:
                Error Trace:    /home/centos/Bhimrao/jaeger-operator/pkg/storage/elasticsearch_secrets_test.go:172
                Error:          Should be true
                Test:           TestWriteToWorkingDir
--- FAIL: TestWriteToWorkingDir (0.00s)

=== RUN   TestExtractSecretsToFile_Err
value of patherr:
 value of ok:
 value of t:
<nil> false &{{{{0 0} 0 0 0 0} [] {0xc0005824e0} false false false false map[] map[] []  [] false false 0xc000468e10 false 0 0 testing.tRunner 0xc0004911e0 1 [269646424 269635420 269646120 269641076 283699476 268715236 268926980] TestExtractSecretsToFile_Err {13904101239831930106 5944685519 0x11d90ce0} 0 0xc000040e40 0xc0002c4bd0 [] {0 0}  <nil> 0} false false 0xc000115cc0}    elasticsearch_secrets_test.go:120:
                Error Trace:    /home/centos/Bhimrao/jaeger-operator/pkg/storage/elasticsearch_secrets_test.go:120
                Error:          Should be true
                Test:           TestExtractSecretsToFile_Err
--- FAIL: TestExtractSecretsToFile_Err (0.00s)

Steps to reproduce

Run make test in pp64 architecture

Expected behavior

All test cases should pass in pp64 architecture as well.

Relevant log output

=== RUN   TestWriteToWorkingDir
    elasticsearch_secrets_test.go:172:
                Error Trace:    /home/centos/Bhimrao/jaeger-operator/pkg/storage/elasticsearch_secrets_test.go:172
                Error:          Should be true
                Test:           TestWriteToWorkingDir
    elasticsearch_secrets_test.go:172:
                Error Trace:    /home/centos/Bhimrao/jaeger-operator/pkg/storage/elasticsearch_secrets_test.go:172
                Error:          Should be true
                Test:           TestWriteToWorkingDir
--- FAIL: TestWriteToWorkingDir (0.00s)

=== RUN   TestExtractSecretsToFile_Err
value of patherr:
 value of ok:
 value of t:
<nil> false &{{{{0 0} 0 0 0 0} [] {0xc0005824e0} false false false false map[] map[] []  [] false false 0xc000468e10 false 0 0 testing.tRunner 0xc0004911e0 1 [269646424 269635420 269646120 269641076 283699476 268715236 268926980] TestExtractSecretsToFile_Err {13904101239831930106 5944685519 0x11d90ce0} 0 0xc000040e40 0xc0002c4bd0 [] {0 0}  <nil> 0} false false 0xc000115cc0}    elasticsearch_secrets_test.go:120:
                Error Trace:    /home/centos/Bhimrao/jaeger-operator/pkg/storage/elasticsearch_secrets_test.go:120
                Error:          Should be true
                Test:           TestExtractSecretsToFile_Err
--- FAIL: TestExtractSecretsToFile_Err (0.00s)

Screenshot

No response

Additional context

No response

Jaeger backend version

v1.41.0

SDK

No response

Pipeline

No response

Stogage backend

No response

Operating system

pp64

Deployment model

No response

Deployment configs

[centos@eltp1 jaeger-operator]$ cat /etc/os-release
NAME="CentOS Stream"
VERSION="8"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="8"
PLATFORM_ID="platform:el8"
PRETTY_NAME="CentOS Stream 8"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:8"
HOME_URL="https://centos.org/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux 8"
REDHAT_SUPPORT_PRODUCT_VERSION="CentOS Stream"
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs-triage New issues, in need of classification
Projects
None yet
Development

No branches or pull requests

2 participants