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

Producing comparison report fails on some exercises #35

Closed
PasiSa opened this issue Sep 6, 2022 · 3 comments
Closed

Producing comparison report fails on some exercises #35

PasiSa opened this issue Sep 6, 2022 · 3 comments
Assignees
Labels
Milestone

Comments

@PasiSa
Copy link
Contributor

PasiSa commented Sep 6, 2022

As noticed in Y1 course, comparison report fails to complete on some exercises, while succeeds on others. In failed cases the exercise list shows 1 invalid submissions, while rest remain in pending state. Need to investigate what causes this (out of memory? or something else?) and then fix it.

@PasiSa PasiSa self-assigned this Sep 6, 2022
@PasiSa PasiSa moved this to Todo in A+ sprints Sep 6, 2022
@markkuriekkinen
Copy link
Contributor

I consider this a duplicate of #13, though it is not yet certain if the memory error causes all these failures in the report.

@PasiSa PasiSa added this to the Fall 2022 milestone Sep 6, 2022
@PasiSa PasiSa closed this as completed in f4b4662 Sep 14, 2022
Repository owner moved this from Todo to Done in A+ sprints Sep 14, 2022
@PasiSa
Copy link
Contributor Author

PasiSa commented Sep 14, 2022

For the record, I don't think this was duplicate of #13 , so we should keep it still open

@markkuriekkinen
Copy link
Contributor

For the record, I don't think this was duplicate of #13 , so we should keep it still open

Yes, correct. This issue focused on that simple one-line bug, using non-existent attribute of an exception. #13 is about the potential excessive memory consumption.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Done
Development

No branches or pull requests

2 participants