Norbert Melzer
Norbert Melzer
As I said earlier, I consider it important to be able to keep track of track local evolutions of the test suite against the same canonical test data. Be it...
> A reminder that the aim here is that the files that get to the student or get to the analyzer have the version. Thats bad… I'd hoped it were...
> The correct version is the version their solution is git-tagged with. Which in no way can be resolved to the version of the problem spec the exercise is based...
I think we can close this. I've already had issues because of this and now am back to a classical testrunner.
As I had pending PRs on erlang and wanted a quick solution, I didn't delve into it. The original error was that I was unable to use `fetch` for the...
As in the meantime all tracks that had a journeyscript in place have changed their testing to simply iterate the `exercises` folder or reading the `config.json` to extract the exercises,...
So there is basically no flake support?
But which configuration file does it take from the flake then?
What do I need to specify the flake for then? I could just specify that one configuration file. Seems as if I totally misunderstood this tool.
You basically need to bump the `Cargo.lock` everytime you change the Version in the `Cargo.toml`, as the version of the package self is part of the lock. Running `cargo build`...