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

FAIL: test_run (github.test_issue_2427.issue_2427_BmffImage_brotliUncompress_memleak.test_run #2788

Closed
norbertwg opened this issue Oct 2, 2023 · 3 comments

Comments

@norbertwg
Copy link
Contributor

Some of the checks fail in my pull requests. Local tests with ctest -C Release --test-dir build --output-on-failure and python3 runner.py complete successfully. I also do not find the test in test folder, so I was not able to search for the root cause of this failure. Anyhow I am pretty sure, that this failure is not related to my code changes (e.g. adding two lenses in nikonmn_int.cpp).

Here the output:

======================================================================
FAIL: test_run (github.test_issue_2427.issue_2427_BmffImage_brotliUncompress_memleak.test_run)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/runner/work/exiv2/exiv2/tests/system_tests.py", line 652, in test_run
    self.compare_stderr(i, command, processed_stderr, stderr)
  File "/Users/runner/work/exiv2/exiv2/tests/system_tests.py", line 773, in compare_stderr
    self._compare_output(
  File "/Users/runner/work/exiv2/exiv2/tests/system_tests.py", line 745, in _compare_output
    self.assertMultiLineEqual(
AssertionError: 'Exiv[61 chars]/exiv2/test/data/issue_2427_poc.jpg:\n_ERROR_FORMAT_CL_SPACE\n' != 'Exiv[61 chars]/exiv2/test/data/issue_2427_poc.jpg:\nCL_SPACE\n'
  Exiv2 exception in print action for file /Users/runner/work/exiv2/exiv2/test/data/issue_2427_poc.jpg:
- _ERROR_FORMAT_CL_SPACE
+ CL_SPACE
 : Standard error does not match
@kmilos
Copy link
Collaborator

kmilos commented Oct 2, 2023

Duplicate of #2762 and #2763

Please search before opening new issues.

@kmilos kmilos closed this as not planned Won't fix, can't repro, duplicate, stale Oct 2, 2023
@norbertwg
Copy link
Contributor Author

Sorry, but from descriptions in #2762 and #2763, I did not see, that they are describing the same problem.

@neheb
Copy link
Collaborator

neheb commented Oct 13, 2023

both describe the same. The problem is upstream changing the error code. Needs to be handled or disabled in the test suite.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants