Gigasecond tests timing out

[oxe-i]

When testing the gigasecond exercise in the online editor, the tests were timing out. I was able to reproduce this error locally using ./bin/verify-exercises-in-docker.

Removing a custom macro I had added to the test file solved the issue locally. However, tests keep timing out in the online editor.

It is possible that the issue is related to the use of the datetime macro, that is defined in Std.Time. But it's only a guess. Since the tests succeed locally, I have no way to be sure other than pushing changes and checking the result on the site.

[oxe-i]

Since we are close to inviting other maintainers to test the track, it might be worth setting the status of the exercise to "wip" until we can solve this issue.

[keiravillekode]

We can locally confirm that gigasecond takes a long time using

time bin/verify-exercises camicia
time bin/verify-exercises gigasecond

Even with only one test case, gigasecond takes much more than 2 camicias to run.

[oxe-i]

Thank you, @keiravillekode

The problem is indeed with the macro. Which is strange, considering it is an "official" macro, from the standard library itself. After constructing PlainDateTime directly, times reduced from ~9s to ~2s.