-
Notifications
You must be signed in to change notification settings - Fork 81
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
Revert "set, then unset, pending pipelinerun regardless of concurrency limit in startPR" #1331
Conversation
…y limit in startPR" This reverts commit 13aa6e5.
Golang test coverage difference reportCoverage decreased by Package report
|
where do you see the flakyness? reporting status or triggerin the run? |
it's on e2e nightly we have seen random failures where the tests, we are getting things like:
and stuck as Pending or as Error, i can't find any other reasons why would it happen and just wondering if that commit was the one triggering a bug in tektoncd/pipeline.. i was mentioning this to a message to @vdemeester :
anyway let's have a try and see if it still randomly failing on mornings. |
This reverts commit 13aa6e5.
We have seen a lot of nightly issues lately and would like to figure out if the
issues is this commit.
Let's keep this for a little while to see if our failures flakyness gets away.
Changes
Submitter Checklist
make test
before submitting a PR (ie: with pre-commit, no need to waste CPU cycle on CI. (or even better install pre-commit and dopre-commit install
in the root of this repo).make lint
before submitting a PR. The markdownlint error can get usually fixed by runningmake fix-markdownlint
(make sure it's installed first)