Enabling the Roc track for testing?

It was already set-up, except for requiring PRs.

1 Like

All three are invited to the GitHub team. Once accepted, they should be able to access the track.

1 Like

I have requested a track Icon here: Requesting a track logo for the Roc language · Issue #180 · exercism/website-icons · GitHub
Is that the right place?

Yes. Thanks. I’ll try and do it on Wednesday. Pestering me here on Wednesday, Thursday and Friday if I’ve still not done it will be appreciated :slight_smile:

3 Likes

Hi @ErikSchierboom , all three (isaacvando, smores56, and bsassoli) have accepted the invitation and now appear in the Roc team on github (see Sign in to GitHub · GitHub), but they tell me they’re still getting a 404 at https://exercism.org/tracks/roc
Is there something else we need to do?

2 Likes

That means there’s a bug in my code unfortunately. I’ll look into it next week

1 Like

Thanks @ErikSchierboom .

Fixed! They’re all maintainers in the DB now so should be able to see the track.

1 Like

Awesome, thanks @ErikSchierboom .

Unrelated question: do the .meta/Example.roc files appear anywhere on exercism.org or are they only used to validate that the test cases work well?

The latter.

1 Like

Hi! It worked, the three testers have access to the Roc track for testing, thanks again @ErikSchierboom .
We all went through several exercises, both via the editor and via the CLI, everything went very smoothly.
Isaac also asked for mentoring, to test that process, but it’s not possible to sign up as a mentor yet, apparently, since the track is not yet public.

I think the only thing missing now is the track icon. @iHiD , here’s the pestering you asked for! :sweat_smile:

1 Like

Until the track goes live, you can’t sign up as a mentor for the public queue since there isn’t one really. I’d try making direct mentoring request links and sending them to one another. Those are automatically generated under the code review tab of the exercise’s page (Exercism as an example of where to look). The URLs look like https://exercism.org/mentoring/external_requests/<long_uuid>. You send the link, the other party opens it, and they can accept your request. That starts a mentoring session with you and from there on, it’s no different from the usual mentoring workflow.

1 Like

Thanks @BNAndras , I’ll try that now.

Has anybody else experienced the following?

An icon showed that an exercise I had previously solved had been updated.

The change was in the test, I think it was an update from 0.14.0 to 0.15.0

app [main] {
    pf: platform "https://github.com/roc-lang/basic-cli/releases/download/0.15.0/SlwdbJ-3GR7uBWQo6zlmYWNYOxnvo8r6YABXD-45UOw.tar.br",
}

After clicking the button to update, the website was showing that my solution had failed:

We received the following error when we ran your code:
Downloading https://github.com/roc-lang/basic-cli/releases/download/0.15.0/SlwdbJ-3GR7uBWQo6zlmYWNYOxnvo8r6YABXD-45UOw.tar.br
    into /root/.cache/roc/packages

── HTTP ERROR in /mnt/exercism-iteration/hello-world-test.roc ──────────────────

I tried to download from this URL:

    https://github.com/roc-lang/basic-cli/releases/download/0.15.0/SlwdbJ-3GR7uBWQo6zlmYWNYOxnvo8r6YABXD-45UOw.tar.br

But I encountered a network error:

    error sending request for url (https://github.com/roc-lang/basic-cli/releases/download/0.15.0/SlwdbJ-3GR7uBWQo6zlmYWNYOxnvo8r6YABXD-45UOw.tar.br): error trying to connect: dns error: failed to lookup address information: Temporary failure in name resolution

After making a whitespace change and clicking ‘Run Tests’, it passed.

The Roc language was recently updated (e.g., to support Task out of the box, add a new ? operator, and more). Updating to the latest Roc version requires also updating to version 0.15.0 of the basic-cli platform, which is used in the tests.
Since the roc-test-runner always uses the latest version of the language (there are no versioned releases yet), we had to update all the exercises to basic-cli 0.15.0. We also updated the roc-test-runner to make it download basic-cli 0.15.0 instead of 0.14.0.
The error you got seems to show that the website was using the previous version of the roc-test-runner. After changing a whitespace in your solution and clicking ‘Run Tests’, it seems that the correct version of the roc-test-runner was used.
Perhaps there’s a bug in the test runner caching?

Hi @iHiD, here’s my daily pestering for the Roc track icon! :blush:

2 Likes

Thanks @iHiD , the Roc track icon looks great! :heart_eyes:

1 Like

My pleasure. Thanks for the pestering! :slight_smile: