I tried to solve the Lucian’s Luscious Lasagna via CLI and got Failed, although all tests passed. I then continued in editor and got a big red EN ERROR OCCURED with following details:
We received the following error when we ran your code:
lucians-luscious-lasagna> test (suite: test)
expectedMinutesInOven [✔]
preparationTimeInMinutes [✔]
elapsedTimeInMinutes [✔]
Finished in 0.0002 seconds
3 examples, 0 failures
lucians-luscious-lasagna> Test suite test passed
Completed 2 action(s).
Where is the error?
BTW, I got the same behavious for Temperatur as well as Pac-Man Rules.
I would probably request review/mentoring on the track and see if you can get feedback from them, as they will see your code. Mention what you are observing in the first comment, so that they get what is wanted to be accomplished there is not necessarily a review for the solution, but an explanation or report that something is strange.
I just checked the queue for the name used here, but do not see any in the queue to look.
They will also see the messages that are given on the platform for that session as well as each iteration.
@tofische are the tests also failing locally, or only when you submit the exercise? This could be completely irrelevant here, apologies if so, but I often receive timeouts on submission, on the Haskell track.
Those exercises are marked as WIP or beta status. WIP exercises aren’t shown to students, but they should be visible to track maintainers and maintainers from other tracks. However if concept_exercises isn’t turned on, it’s unclear where you’re seeing the exercises.
I’m a maintainer on other tracks and an insider, and I don’t see any of concept exercises on the Haskell track page. Are you a Haskell maintainer? That might be why you’re seeing something different.
Are you saying comment out the exercises until they’re ready? That seems a lot of extra work.
My understanding is that Julia stages draft concept exercises in exercises/concepts.wip. When they’re ready to be a concept exercise, they’re moved to exercises/concept and added to the track config file. That piecemeal approach helps avoids configlet warnings along the way, and it’s more ergonomic in my opinion that adding a lot of placeholder entries which Cairo did.