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

Concurrent tests of native backend fail with: lost signal due to full pipe: 11 #53

Open
1 of 3 tasks
ivogabe opened this issue Dec 12, 2019 · 0 comments
Open
1 of 3 tasks
Labels

Comments

@ivogabe
Copy link
Contributor

ivogabe commented Dec 12, 2019

I am submitting a...

  • bug report
  • feature request
  • support request => you might also like to ask your question on the mailing list or gitter chat.

Description

The tests of the native backend fail on multicore architectures. The problem appears to occur when multiple test cases are ran in parallel. If you let the test suite execute the tests sequentially, they do pass. Note that the different tests are then sequential, but each test case may be executed on multiple threads.

I also tried to revert the recent changes

Expected behaviour

Tests pass. When multiple computations are given to accelerate at a time, it will let the set of worker threads work on both computations at the same time. I think that this cooperation has some bug.

Current behaviour

The threads fail by printing the following the console many times:

nofib-llvm-native: lost signal due to full pipe: 11

I think some test case fails, which causes that the process becomes in some invalid state, causing that the later tests will also fail with this error.

It may also happen the test suite stops at some test. It looks like the same error, but the test case will then not run the other tests any more.

        DIM3
          sum:                nofib-llvm-native: SignalException 11

I did verify that the recent change in the scheduler did not influence this. Also, the refactoring of tuples seems unrelated.

Possible solution (optional)

Steps to reproduce (for bugs)

  1. Run the tests on a machine with enough cores

Your environment

I ran the tests on our shared machine.

@ivogabe ivogabe added the bug label Dec 12, 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

1 participant