Skip to content

GitHub tests failing for some mysterious reason #498

Description

@bhaller

Hi @currocam. I have need of your superpowers once again.

Tests just started failing on the branch I'm working on, multichrom, as evidenced by this:

https://github.com/MesserLab/SLiM/actions/runs/14052089256/job/39344856600

Annoyingly, it just says that the SLiM tests have failed; it doesn't show me the actual output from the failed tests, so I have no idea which tests, out of the tens of thousands that SLiM runs, are failing. It says to use "--rerun-failed --output-on-failure" to re-run the failed cases verbosely, but naturally it does say where or how to set those flags, nor can I find any help in Google on how to do so. (People who write error messages like this ought to be court-martialled! Not that I'm not guilty of it myself. :->)

Normally, in this situation, the tests fail for me locally as well, so I can just see what the problem is on my own machine and fix it. But – for the first time ever, I think – the tests are failing on GitHub, but not on my local machine, and so now I'm flummoxed. How do I set those flags and see what's failing? I hope you can help! If you're busy, no worries; I'll try other folks who might know, but you always seem so good at this kind of thing! If there's a way to just set "--output-on-failure" for all tests always, that would be good; I can't imagine why that isn't the default. Who wants tests to fail and receive no output regarding what failed or why?

Thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions