Created attachment 635712 [details] test failure log (gzipped) Test failure: proper_tests:980: false_props_test_...*failed* in function proper_tests:'-false_props_test_/0-fun-419-'/1 (test/proper_tests.erl, line 980) in call from proper_tests:'-false_props_test_/0-fun-429-'/0 (test/proper_tests.erl, line 980) in call from eunit_test:run_testfun/1 (eunit_test.erl, line 71) in call from eunit_proc:run_test/1 (eunit_proc.erl, line 510) in call from eunit_proc:with_timeout/3 (eunit_proc.erl, line 335) in call from eunit_proc:handle_test/2 (eunit_proc.erl, line 493) in call from eunit_proc:tests_inorder/3 (eunit_proc.erl, line 435) in call from eunit_proc:with_timeout/3 (eunit_proc.erl, line 325) **error:{assertMatch,[{module,proper_tests}, {line,980}, {expression,"proper : check ( ets_counter : prop_ets_counter ( ) , CExm1 , [ ] )"}, {pattern,"false"}, {value,{error,non_boolean_result}}]} My motivation to debug erlang tests is limited, so I'm wondering if we should just RESTRICT="test" this package. I looked into upstream's repo, plenty of changes since the last release and I can reproduce the test failure without portage. With the latest git code I get *more* test failures than with the last release.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=792a1b81e0868a0fc2f23b68ad89e9a7dbe4667d commit 792a1b81e0868a0fc2f23b68ad89e9a7dbe4667d Author: Hanno Böck <hanno@gentoo.org> AuthorDate: 2020-07-01 12:08:48 +0000 Commit: Hanno Böck <hanno@gentoo.org> CommitDate: 2020-07-01 12:08:48 +0000 dev-erlang/proper: Disable tests Broken upstream with latest erlang. Closes: https://bugs.gentoo.org/720472 Signed-off-by: Hanno Böck <hanno@gentoo.org> Package-Manager: Portage-2.3.103, Repoman-2.3.23 dev-erlang/proper/proper-1.3.ebuild | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
