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

Pytest failure in main (after #388 was merged) and #418 #420

Closed
andrii-i opened this issue Aug 12, 2023 · 1 comment · Fixed by #424
Closed

Pytest failure in main (after #388 was merged) and #418 #420

andrii-i opened this issue Aug 12, 2023 · 1 comment · Fixed by #424
Assignees
Labels
bug Something isn't working
Milestone

Comments

@andrii-i
Copy link
Collaborator

Description

Reproduce

See CI run : https://github.com/jupyter-server/jupyter-scheduler/actions/runs/5837424752/job/15832930590

@andrii-i andrii-i added the bug Something isn't working label Aug 12, 2023
@JasonWeill JasonWeill added this to the 2.1.0 milestone Aug 14, 2023
@JasonWeill JasonWeill self-assigned this Aug 14, 2023
@JasonWeill
Copy link
Collaborator

The underlying issue seems to be that when using the archiving scheduler, the "output" filenames are not used; the tarball contains files named with "staging" filenames. This does not cause a problem when run in production, but it breaks the tests. See #421 for a possible fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
2 participants