emacs FTBFS on s390x because of a failing unit test
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
emacs (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Groovy |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
As a follow up to bug #1911209, the following test is failing reliably on s390x only:
Running 6 tests (2021-01-12 15:32:18+0000, selector `(not (or (tag :expensive-test) (tag :unstable)))')
passed 1/6 lcms-ciecam02-gold (0.000133 sec)
Test lcms-cri-cam02-ucs backtrace:
signal(
ert-fail(((should (eql 0.0 (lcms-cam02-ucs '(0.5 0.5 0.5) '(0.5 0.5
#f(compiled-
ert--
ert-run-
ert-run-
ert-run-
ert-run-
ert-run-
eval(
command-
command-line()
normal-
Test lcms-cri-cam02-ucs condition:
(ert-
((should
(eql 0.0
(lcms-
:form
(eql 0.0 3.4662020221023
:value nil))
FAILED 2/6 lcms-cri-cam02-ucs (0.000129 sec)
passed 3/6 lcms-dE-
passed 4/6 lcms-jmh-
passed 5/6 lcms-roundtrip (0.000068 sec)
passed 6/6 lcms-whitepoint (0.000056 sec)
Ran 6 tests, 5 results as expected, 1 unexpected (2021-01-12 15:32:18+0000, 0.088409 sec)
1 unexpected results:
FAILED lcms-cri-cam02-ucs
summary: |
- emacs 27.1 FTBFS in hirsute on s390x because of a failing unit test + emacs FTBFS on s390x because of a failing unit test |
Changed in emacs (Ubuntu Groovy): | |
status: | New → Won't Fix |
Changed in emacs (Ubuntu): | |
assignee: | nobody → Olivier Tilloy (osomon) |
Changed in emacs (Ubuntu): | |
status: | New → Fix Released |
That test is not new, it was present in emacs 1:26.3+1-1ubuntu2 (the version currently in the release pocket) and it used to pass. From a cursory glance, I didn't spot relevant changes in upstream code that would explain the regression, so this needs further investigation.