make test-suite outputs some errors

Open
#112 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
c, git, shell
Domain
build-system, testing-qa

Research direction

Start in tests/run-test-suite/Makefile around line 28 and reproduce the command sequence shown in the issue. Investigate how the existing run-test-suite-code branch and test worktree are handled; done means the test suite completes without fatal Git errors or ignored Makefile failures.

Written by the indexing model from the issue text.

Description

Tests succeed, but I get these errors:

make -C tests/run-test-suite test
make[1]: Entering directory '/tmp/libyaml/tests/run-test-suite'
git branch --track run-test-suite-code origin/run-test-suite-code
fatal: A branch named 'run-test-suite-code' already exists.
Makefile:28: recipe for target 'code' failed
make[1]: [code] Error 128 (ignored)
git worktree prune
git worktree add test run-test-suite-code
fatal: 'test' already exists
Makefile:28: recipe for target 'code' failed
make[1]: [code] Error 128 (ignored)
(cd test && git reset --hard c0a4e7a388658bffa53078a6ac28b3d2e118861b)
HEAD is now at c0a4e7a Initial commit
prove -lv test
test/libyaml-emitter.t .......
ok 1 229Q: Spec Example 2.4. Sequence of Mappings
...
Dominant language
C
Stars
1.2k
Forks
370
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 yaml/libyaml

All issues in yaml/libyaml

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.