Skip to content

cargo test -p payjoin fails #1019

Closed

Description

@nothingmuch

8ceccaa broke test builds with the default features:

error[E0432]: unresolved import `crate::send::v1`
   --> payjoin/src/core/send/v2/session.rs:108:22
    |
108 |     use crate::send::v1::SenderBuilder;
    |                      ^^ could not find `v1` in `send`
    |

Activity

  1. nothingmuch commented on Aug 29, 2025

    @nothingmuch
    ContributorAuthor
  2. DanGould commented on Aug 29, 2025

    @DanGould
    Member

    The session tests must not use v1::SenderBuilder. Use v2 with NoOp persister.

  3. added
    bugSomething isn't working
    good first issueDoes NOT mean "an LLM can do this." Please discuss the constraints and intended approach.
    on Aug 29, 2025
  4. DanGould commented on Aug 29, 2025

    @DanGould
    Member

    I wonder why this isn't tested by CI

  5. nothingmuch commented on Aug 29, 2025

    @nothingmuch
    ContributorAuthor

    because payjoin/contrib/test.sh only tests with --all-features

  6. self-assigned this
    on Sep 2, 2025
  7. benalleng commented on Sep 2, 2025

    @benalleng
    Collaborator

    Going to take this and look into adding a test suite that doesn't use --all-features

  8. benalleng commented on Oct 29, 2025

    @benalleng
    Collaborator

    The exact error linked #1019 (comment) has actually been resolved as of d6ab28d however several other errors still exist when running cargo test -p payjoin

  9. Arowolokehinde commented on Mar 20, 2026

    @Arowolokehinde
    Contributor

    hi @DanGould and @nothingmuch @benalleng has this issue been resolved ?
    i would like to take a look at the other errors

  10. benalleng commented on Mar 24, 2026

    @benalleng
    Collaborator

    I believe that #1036 should really close this, feel free to give that PR a test, as for other issues, take a look at maybe some more recent ones and just start asking questions!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't workinggood first issueDoes NOT mean "an LLM can do this." Please discuss the constraints and intended approach.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions