Skip to content

JPERF-811: Show how flaky shouldTolerateEarlyFinish is, so that it's … - #24

Closed
pczuj wants to merge 1 commit into
masterfrom
JPERF-811-show-how-flaky-SshTest-shouldTolerateEarlyFinish-is
Closed

JPERF-811: Show how flaky shouldTolerateEarlyFinish is, so that it's …#24
pczuj wants to merge 1 commit into
masterfrom
JPERF-811-show-how-flaky-SshTest-shouldTolerateEarlyFinish-is

Conversation

@pczuj

Copy link
Copy Markdown
Contributor

…clear that next change fixes it

@pczuj
pczuj requested a review from a team as a code ownerJune 22, 2022 16:20
@pczujpczuj closed this Jun 22, 2022
@pczuj
pczuj deleted the JPERF-811-show-how-flaky-SshTest-shouldTolerateEarlyFinish-is branch June 22, 2022 16:24
@pczuj

Copy link
Copy Markdown
ContributorAuthor

The test will be fixed in #23


val fail = sshHost.runInBackground("nonexistent-command")
val failResult = fail.stop(Duration.ofMillis(20))
repeat(1000) {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good change, exposes the problem more predictably 👍

@dagguh

Copy link
Copy Markdown
Contributor

This PR left an unmaintained branch. It's best to open PRs from forks.

@pczuj

Copy link
Copy Markdown
ContributorAuthor

This PR left an unmaintained branch.

No, I believe I removed the branch. Don't see it in the picker:
Screenshot 2022-06-29 at 14 39 48

It's best to open PRs from forks.

I don't see any advantage and it's easier to access other's changes with vanilla git client when most of the PR branches land in the main repository. I'm open to discussion about it. Maybe I don't know about something.

@dagguh

Copy link
Copy Markdown
Contributor

Ah right, it's a different branch 👍

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@pczuj@dagguh