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

Either fix ert failures or mark them as expected #1201

Closed
temyurchenko opened this issue Apr 10, 2024 · 4 comments
Closed

Either fix ert failures or mark them as expected #1201

temyurchenko opened this issue Apr 10, 2024 · 4 comments

Comments

@temyurchenko
Copy link
Contributor

Expected behavior

Running cask exec ert-runner results in no failing tests.

Actual behavior

First, ert-runner complains about duplicated test names. However, even after we fix those, we get 42 failures. The best and simplest way to deal with those is to mark them as «expected failures». It is slightly complicated due to some tests being wrapped in macros.

Steps to reproduce the problem

Run cask build followed by cask exec ert-runner.

Backtraces if necessary (M-x toggle-debug-on-error)

Environment & version information

  • smartparens version: 20231024.1804
  • Active major-mode: fundamental-mode
  • Smartparens strict mode: nil
  • Emacs version (M-x emacs-version): GNU Emacs 29.2 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.40, cairo version 1.18.0)
  • Starterkit/Distribution: Vanilla
  • OS: gnu/linux
@github-project-automation github-project-automation bot moved this to To triage in Triage Apr 10, 2024
@temyurchenko temyurchenko changed the title Either fix ert failures or mark Either fix ert failures or mark them as expected Apr 10, 2024
@Fuco1
Copy link
Owner

Fuco1 commented Apr 10, 2024

The failing test cases need to be corrected, they should not be failing. I am slowly fixing some but it's a long process.

@Fuco1 Fuco1 moved this from To triage to Backlog in Triage Apr 10, 2024
@temyurchenko
Copy link
Contributor Author

The failing test cases need to be corrected, they should not be failing. I am slowly fixing some but it's a long process.

Oh, yes, I absolutely get that. Sorry, if that sounded pressuring. I was just reading the contributing guide, which advised to run a test-suite, which I ran and it showed a lot of errors. I haven't found any documentation about that in the repo, so I decided to make an issue for others who might be confused.

@Fuco1
Copy link
Owner

Fuco1 commented Apr 10, 2024

No worries :)

Fuco1 added a commit that referenced this issue Apr 10, 2024
fix some of the tests; partially addresses #1201
@Fuco1
Copy link
Owner

Fuco1 commented Apr 10, 2024

I'll make a new issue with all the failing tests so I can track progress individually.

@Fuco1 Fuco1 closed this as completed Apr 10, 2024
@github-project-automation github-project-automation bot moved this from Backlog to Done in Triage Apr 10, 2024
@Fuco1 Fuco1 mentioned this issue Apr 10, 2024
38 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

No branches or pull requests

2 participants