AccelerateHS / AccelerateHS/accelerate-llvm

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

Abierto
#53 0 comentarios 0 reacciones 0 asignados Ver en GitHub
bug
Lenguaje dominante
Haskell
Estrellas
171
Forks
65
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

I am submitting a...
- [x] bug report
- [ ] feature request
- [ ] support request => you might also like to ask your question on the [mailing list](mailto:accelerate-haskell@googlegroups.com) or [gitter chat](https://gitter.im/AccelerateHS/Lobby).

## 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.

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.