building from source: failed test suite

Open
#38 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
20/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
go
Domain
cli, testing-qa

Research direction

Start with the attached exercism-log.txt and TestExerciseDir in workspace_test.go around line 142. Reproduce the source build and test suite in the reported Debian environment, then compare the failure with the expected and actual exercise directory values. Done means determining whether this is a program issue or an unsupported environment and documenting that conclusion.

Written by the indexing model from the issue text.

Description

Hello. Today I tried to package exercism for Debian, an, while procedure is very automated, I encountered test suite failures. Can you please take a look at log and evaluate, whether there is actually issue in program or I am doing something wrong/my environment is unsupported?

I included whole log just in case, the most interesting part (I think) is on bottom (there are more in log):

    workspace_test.go:142:
                Error Trace:    workspace_test.go:142
                Error:          Not equal:
                                expected: "exercise"
                                actual  : ""

                                Diff:
                                --- Expected
                                +++ Actual
                                @@ -1 +1 @@
                                -exercise
                                +
                Test:           TestExerciseDir
                Messages:       exercise/in/a
FAIL
FAIL    github.com/exercism/cli/workspace       0.017s

exercism-log.txt

Dominant language
No language data
Stars
3
Forks
3
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from exercism/support

All issues in exercism/support

Similar issues

More CLI issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.