Testcases - testModuleData fails on armv7hl architecture

Open
#106 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
c, python

Research direction

Start with tests.py:TestYara.testModuleData at line 989 and reproduce the targeted nosetests command from the build log on armv7hl. Trace why the constants assertion differs on that architecture; done means testModuleData passes there while the other listed tests remain passing.

Written by the indexing model from the issue text.

Description

Hello,
the test case testModuleData is failing on the armv7hl architecture.
https://kojipkgs.fedoraproject.org//work/tasks/263/33620263/build.log:

+ PYTHONPATH=/builddir/build/BUILDROOT/python-yara-3.9.0-1.fc31.arm//usr/lib/python3.7/site-packages/
+ /usr/bin/nosetests-3.7 -v ./tests.py:TestYara.testCompare ./tests.py:TestYara.testModuleData ./tests.py:TestYara.testEntrypoint ./tests.py:TestYara.testIn ./tests.py:TestYara.testIntegerFunctions ./tests.py:TestYara.testCompileFile
testCompare (tests.TestYara) ... ok
testModuleData (tests.TestYara) ... FAIL
testEntrypoint (tests.TestYara) ... ok
testIn (tests.TestYara) ... ok
testIntegerFunctions (tests.TestYara) ... ok
testCompileFile (tests.TestYara) ... ok
======================================================================
FAIL: testModuleData (tests.TestYara)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/builddir/build/BUILD/yara-python-3.9.0/tests.py", line 989, in testModuleData
    self.assertTrue(data['constants']['one'] == 1)
AssertionError: False is not true

Dominant language
C
Stars
754
Forks
190
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from VirusTotal/yara-python

All issues in VirusTotal/yara-python

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.