Sync line-up tests - #1141
Conversation
|
This PR touches files which potentially affect the outcome of the tests of an exercise. This will cause all students' solutions to affected exercises to be re-tested. If this PR does not affect the result of the test (or, for example, adds an edge case that is not worth rerunning all tests for), please add the following to the merge-commit message which will stops student's tests from re-running. Please copy-paste to avoid typos. For more information, refer to the documentation. If you are unsure whether to add the message or not, please ping |
|
I'm confused. Issue #1109 was dated Apr 14, but this exercise was only added to the Julia track on July 27. An update is needed, but in response to changes in Given all the close timings, the exercise may have been generated from a stale cache of In this PR,
There is a Jinja2 template, and tests are updated with Edit: the tests were fine, so |
|
There are only 21 completions on this recently-added exercise, so re-running tests is low-cost. |
|
Oops, I didn't realize there was a generator so yeah I added the new tests by hand. As for the linked issue, it was first created April 14, but it's automatically edited on a schedule to reflect the unsynced tests at the time of the edit. So the line-up tests are showing up now, but they wouldn't have been in the original GitHub issue from April 14. I tend to close the issue on my tracks once tests are synced so the bot creates a fresh issue. That's a bit less confusing. |
Recent (both Julia and R), with many thanks to @BethanyG for implementing them. |
2 participants
Related to #1109