Subject: Re: bug#48350: 28.0.50; bytecomp-tests--dest-mountpoint test failure

From: Lars Ingebrigtsen <[email-masked]>
Date: Thu, 12 Aug 2021 01:06:42 +0200

Lars Ingebrigtsen <[email-masked]> writes:

> Most puzzling.  And it's even more frustrating that it's impossible to
> get anything sensible out of the failing instance -- it fails when
> trying to load stuff to report the error, I think?

Yes, indeed, and that's because --batch now outputs a backtrace, which
loads debug.el, and since we're in a chroot, Emacs can't load that file?

So I disabled that, and got the real error:

Test bytecomp-tests--dest-mountpoint condition:
    (ert-test-failed
     ((status . 255)
      (output . "Creating directory with prefix: Read-only file system, /home/larsi/src/emacs/trunk/test/emacs-testsuite-\n")))

And...  that's from here?

      ;; When $HOME is set to '/nonexistent' means we are running the
      ;; testsuite, add a temporary folder in front to produce there
      ;; new compilations.
      (when (equal (getenv "HOME") "/nonexistent")
        (let ((tmp-dir (make-temp-file "emacs-testsuite-" t)))
          (add-hook 'kill-emacs-hook (lambda () (delete-directory tmp-dir t)))
          (push tmp-dir native-comp-eln-load-path))))

Hm...  is there no way to disable all the nativecomp stuff?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no