I ran the tests on m68k, where they were many failures, but the package installed anyway. Seemingly the exit status from run.py cannot be trusted. The ebuild also creates a file called node_failed.txt to write the failures to, but this file remained empty. Instead, another file called failed.txt was populated with the failures. I therefore don't think the "touch" line is needed any more.
I ran into the same issue on amd64 and riscv.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=2a103afad637fb46659a8b1d6ef048be8721b13b commit 2a103afad637fb46659a8b1d6ef048be8721b13b Author: Aliaksei Urbanski <aliaksei.urbanski@gmail.com> AuthorDate: 2024-06-24 22:32:22 +0000 Commit: Maciej Barć <xgqt@gentoo.org> CommitDate: 2024-06-24 23:01:45 +0000 dev-python/js2py: revbump to 0.74-r1 These changes: - fix CVE-2024-28397 - fix ignoring of test failures - restrict the test feature since multiple tests are broken Bug: https://bugs.gentoo.org/831356 Signed-off-by: Aliaksei Urbanski <aliaksei.urbanski@gmail.com> Closes: https://github.com/gentoo/gentoo/pull/37285 Signed-off-by: Maciej Barć <xgqt@gentoo.org> .../js2py/files/js2py-0.74-CVE-2024-28397.patch | 21 +++++++++++++++++++ .../{js2py-0.74.ebuild => js2py-0.74-r1.ebuild} | 24 ++++++++++++++-------- 2 files changed, 36 insertions(+), 9 deletions(-)
