Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

missing documentation: how to run CloudSlang on powerbook #175

Open
meshipeer opened this issue Apr 19, 2016 · 0 comments
Open

missing documentation: how to run CloudSlang on powerbook #175

meshipeer opened this issue Apr 19, 2016 · 0 comments
Milestone

Comments

@meshipeer
Copy link
Contributor

meshipeer commented Apr 19, 2016

@ingydotnet

@levice14 levice14 added this to the 0.9.60 milestone May 3, 2016
@meshipeer meshipeer modified the milestones: 1.0, 0.9.60 May 26, 2016
@meshipeer meshipeer modified the milestones: Backlog, 1.0 Aug 21, 2016
ingydotnet pushed a commit to ingydotnet/docs that referenced this issue Jul 28, 2024
* Clarify top-level `fail` in test runner spec

Consider the situation of:
- The user submits a solution in a compiled language
- The user's solution compiles without error
- The first test passes, but the next test "produces an error" (for
  example, it raises an exception).

In this case, the correct top-level status is `fail`, with one
test-level status of `pass`, and one test-level status of `error`. But
the previous wording could imply that a top-level status of `fail`
is only correct if at least one test has the status `fail`.

* Clarify per-test `message` in test runner spec

The previous wording could imply that a per-test `message` property
can only be present when the test `status` is `fail`.

* Clarify top-level `error` in test runner spec

To me, the previous wording implied that a top-level `status` of `error`
is valid when at least one test "errors". But actually, if at least one
test was "executed", the top-level status should be `pass` or `fail`.

* Try to clarify test-level `error` in test runner spec

* Further clarify test-level `message`

Co-authored-by: Erik Schierboom <[email protected]>

* Describe top-level `error` more consistently

Co-authored-by: Erik Schierboom <[email protected]>

* Update building/tooling/test-runners/interface.md

Co-authored-by: ee7 <[email protected]>

Co-authored-by: Erik Schierboom <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants