[ofiwg] [libfabric-users] Fabtest questions

[Hefty, Sean]

> which runs through some tests (all but one pass), and then gets to
> the test seen below. It continues to repeat the server_stdout lines
> forever. Do you have any thoughts on what is happening?
> 
> 
> - name:   fi_poll -t counter -p "verbs"
>   result: Fail
>   time:   91
>   server_cmd: /opt/fabtests/bin/fi_poll -t counter -p "verbs" -s
> enceladus-iw.ofa
>   server_stdout: |
>     fi_cntr_wait(): common/shared.c:1976, ret=-38 (Function not
> implemented)
>     fi_cntr_wait(): common/shared.c:1976, ret=-38 (Function not
> implemented)
>     fi_cntr_wait(): common/shared.c:1976, ret=-38 (Function not
> implemented)
>     fi_cntr_wait(): common/shared.c:1976, ret=-38 (Function not
> implemented)
>     fi_cntr_wait(): common/shared.c:1976, ret=-38 (Function not
> implemented)
>     fi_cntr_wait(): common/shared.c:1976, ret=-38 (Function not
> implemented)
>     fi_cntr_wait(): common/shared.c:1976, ret=-38 (Function not
> implemented)
>     fi_cntr_wait(): common/shared.c:1976, ret=-38 (Function not
> implemented)

Quickly looking at the code, I think the test (or rather common code that it is calling) is incorrect.  The code looks like it is assuming that all counters are associated with wait objects, which is not necessarily the case.

I've opened a github issue to track this.

https://github.com/ofiwg/fabtests/issues/815

- Sean