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

Legacy test failures #550

Closed
mxz297 opened this issue Feb 10, 2019 · 3 comments
Closed

Legacy test failures #550

mxz297 opened this issue Feb 10, 2019 · 3 comments
Assignees
Labels

Comments

@mxz297
Copy link
Member

mxz297 commented Feb 10, 2019

The Dyninst test suite has a couple of test failures that have been around for a long time, ranging from a few months to several years.

If the test itself is wrong, the test should be disabled. Otherwise, I will try to fix Dyninst.

Here is the list for x86-64:

test_pt_ls                        none 64  create   NA      dynamic nonPIC  FAILED (Running Test)
test_pt_ls                        none 64  rewriter NA      dynamic nonPIC  FAILED (Running Test)
test1_22                   g++    none 64  rewriter NA      dynamic PIC     FAILED (Group Teardown)
pc_tls                     g++    none 64  create   SPST    dynamic nonPIC  FAILED (Running Test)
@sashanicolas
Copy link
Contributor

for aarch64:

TEST                       COMP   OPT  ABI MODE     THREAD  LINK    PIC     RESULT
test_pt_ls                        none 64  create   NA      dynamic nonPIC  FAILED (Running Test)
test_pt_ls                        none 64  attach   NA      dynamic nonPIC  SKIPPED
test_pt_ls                        none 64  rewriter NA      dynamic nonPIC  FAILED (Running Test)

@mxz297
Copy link
Member Author

mxz297 commented Feb 12, 2019

@sashanicolas I found that test_pt_ls failed because it cannot find parseThat. I updated the test suite to properly search for parseThat and the test_pt_ls is now passing on my machine. Can you pull the test suite and run it on leela?

@hainest
Copy link
Contributor

hainest commented Mar 7, 2019

Fixed by #549

@hainest hainest closed this as completed Mar 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants