Skip to content

Conversation

@qinsoon
Copy link
Member

@qinsoon qinsoon commented Oct 29, 2020

This PR adds a shorter timeout to avoid any stuck code executed in the job consuming excessive runner minutes.

@qinsoon qinsoon requested a review from javadamiri October 29, 2020 22:20
Copy link
Contributor

@javadamiri javadamiri left a comment

Choose a reason for hiding this comment

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

Looking at the last action which failed after around 8 hours, I think we also need timeouts on jikesrvm-perf-compare and openjdk-perf-compare.
E.g. the later has taken much longer than usual in the last failed test.

@qinsoon
Copy link
Member Author

qinsoon commented Oct 29, 2020

Looking at the last action which failed after around 8 hours, I think we also need timeouts on jikesrvm-perf-compare and openjdk-perf-compare.
E.g. the later has taken much longer than usual in the last failed test.

Yeah, we could. But those run on our self-hosted runner.

@qinsoon qinsoon merged commit 1c806b4 into master Oct 30, 2020
@qinsoon qinsoon deleted the timeout-github-runner branch October 30, 2020 00:35
qinsoon pushed a commit to qinsoon/mmtk-core that referenced this pull request Mar 28, 2023
…mmtk#158)

MarkCompactAllocator mistakenly used the offset for `bump_allocator` in
the Allocators struct instead of the offset for `markcompact` in its C2
fastpath. This commit fixes the above issue and refactors the duplicated
offset calculation code in the C1 and C2 fastpaths into a new function.
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

Successfully merging this pull request may close these issues.

3 participants