We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Problem: in #5796, the t2812-flux-job-last.t test got stuck in the test for issue #4930:
t2812-flux-job-last.t
expecting success: flux job last "[:]" >lastdump.exp && flux dump dump.tgz && flux start -o,-Scontent.restore=dump.tgz \ flux job last "[:]" >lastdump.out && test_cmp lastdump.exp lastdump.out flux-dump: archived 1 keys flux-dump: archived 2 keys flux-dump: archived 3 keys flux-dump: archived 4 keys flux-dump: archived 5 keys flux-dump: archived 6 keys flux-dump: archived 7 keys flux-dump: archived 8 keys flux-dump: archived 9 keys flux-dump: archived 65 keys Mar 25 18:41:44.457761 job-manager.err[0]: replay warning: INACTIVE action failed on job fEyxE9d: Read-only file system Mar 25 18:41:44.785969 job-manager.err[0]: sched.alloc-response: id=fF1SDRy already allocated
The text was updated successfully, but these errors were encountered:
duplicate of #5815?
Sorry, something went wrong.
Oh indeed, sorry, missed that one.
No branches or pull requests
Problem: in #5796, the
t2812-flux-job-last.t
test got stuck in the test for issue #4930:The text was updated successfully, but these errors were encountered: