Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

buttercup failures on master #1995

Closed
bremner opened this issue Jan 17, 2023 · 9 comments
Closed

buttercup failures on master #1995

bremner opened this issue Jan 17, 2023 · 9 comments

Comments

@bremner
Copy link

bremner commented Jan 17, 2023

Checklist

  • [x ] I have checked existing issues for potential duplicates before creating this one.
  • [x ] I have read the [Troubleshooting guide][].

Bug description

Running "buttercup -L ." with emacs 28.2+1-9 and buttercup 1.26-4
on Debian on commit 15f0759 yields the attached failures.

I also tried

EMACS_INHIBIT_AUTOMATIC_NATIVE_COMPILATION=t emacs -q -batch -L . -l buttercup -f buttercup-run-discover

There are nonetheless the same messages about native compilation (loading) failing.

This is also reported as https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028725

buttercup.log

@jcs090218
Copy link
Member

It should resolve in #2002.

@bremner
Copy link
Author

bremner commented Feb 20, 2023 via email

@jcs090218
Copy link
Member

jcs090218 commented Feb 22, 2023

Interesting... Our CI does not report anything like this. See https://github.com/flycheck/flycheck/actions/runs/4238492328/jobs/7365623154#step:5:878

Edit: How do you invoke the tests? Through Cask, Eask, makem.sh?

@sergiodj
Copy link

sergiodj commented Feb 23, 2023

Debian invokes buttercup -L . directly. I'm also investigating this problem and I noticed something interesting. If I get inside the chroot where the package is being built, set HOME to a proper location (e.g., /tmp/), create the .emacs.d directory, and run buttercup again, I see the same error:

...
========================================
Utilities flycheck-buffer-saved-p considers an unmodified buffer with backing file saved

Traceback (most recent call last):
  spy-on(buffer-file-name :and-return-value "test-buffer-name")
  buttercup--spy-on-and-call-replacement(buffer-file-name (lambda (&rest args) nil '"test-buffer-name"))
  comp-subr-trampoline-install(buffer-file-name)
  comp-trampoline-search(buffer-file-name)
  native-elisp-load("/tmp/.emacs.d/eln-cache/28.2-b25a1857/subr--trampoline-6275666665722d66696c652d6e616d65_buffer_file_name_0.eln")
error: (native-lisp-load-failed "file does not exists" "/tmp/.emacs.d/eln-cache/28.2-b25a1857/subr--trampoline-6275666665722d66696c652d6e616d65_buffer_file_name_0.eln")

========================================
Utilities flycheck-buffer-saved-p considers a modified buffer with backing file unsaved

Traceback (most recent call last):
  spy-on(buffer-file-name :and-return-value "test-buffer-name")
  buttercup--spy-on-and-call-replacement(buffer-file-name (lambda (&rest args) nil '"test-buffer-name"))
  comp-subr-trampoline-install(buffer-file-name)
  comp-trampoline-search(buffer-file-name)
  native-elisp-load("/tmp/.emacs.d/eln-cache/28.2-b25a1857/subr--trampoline-6275666665722d66696c652d6e616d65_buffer_file_name_0.eln")
error: (native-lisp-load-failed "file does not exists" "/tmp/.emacs.d/eln-cache/28.2-b25a1857/subr--trampoline-6275666665722d66696c652d6e616d65_buffer_file_name_0.eln")
...

However, if I inspect the contents of $HOME/.emacs.d, I see:

# tree $HOME/.emacs.d/
/tmp/.emacs.d/
└── eln-cache
    └── 28.2-b25a1857
        └── subr--trampoline-66696c652d6578697374732d70_file_exists_p_0.eln

3 directories, 1 file

So there is a .eln file there, but it's a different one than the one expected by the test. I'm still trying to figure out what's going on here.

@sergiodj
Copy link

After some more investigation, I found that the problem is not with flycheck, but probably with buttercup: jorgenschaefer/emacs-buttercup#230

I'm still puzzled as to why these failures are not reproducible in your CI, though.

@jcs090218
Copy link
Member

May be something went wrong with .eln? I haven't tried native compilation, but I've heard is unstable. 😕 Maybe that was the issue?

@sergiodj
Copy link

It's a new feature but I wouldn't say it's unstable. However, it seems like the Emacs your CI is using doesn't have native compilation enabled, which explains why the error doesn't manifest there.

@jcs090218
Copy link
Member

It's a new feature but I wouldn't say it's unstable.

That's good to know. :)

Yeah, we don't tested with native compilation. That's indeed true. 😅

@bbatsov
Copy link
Contributor

bbatsov commented Feb 11, 2024

The tests are working for me, both locally and on the CI, so I close the issue for now.

@bbatsov bbatsov closed this as completed Feb 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants