-
Notifications
You must be signed in to change notification settings - Fork 194
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
[JEP-210] Integration testing #252
Conversation
Actually from a quick glance it looks like |
A FlowNode was being sent to GraphListener.Synchronous without ArgumentsAction available.
I got a couple failures locally but am unclear how to interpret them. Probably meaningless unless they are known to pass against released updates. org.junit.ComparisonFailure: expected:<[sleep]> but was:<[// parallel]> at org.junit.Assert.assertEquals(Assert.java:115) at org.junit.Assert.assertEquals(Assert.java:144) at org.jenkinsci.plugins.workflow.cps.FlowDurabilityTest.assertIncludesNodes(FlowDurabilityTest.java:664) at org.jenkinsci.plugins.workflow.cps.FlowDurabilityTest$25.evaluate(FlowDurabilityTest.java:887) java.lang.AssertionError: expected:<SUCCESS> but was:<FAILURE> at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.failNotEquals(Assert.java:834) at org.junit.Assert.assertEquals(Assert.java:118) at org.junit.Assert.assertEquals(Assert.java:144) at org.jenkinsci.plugins.workflow.cps.FlowDurabilityTest$30.evaluate(FlowDurabilityTest.java:1000)
Regarding
I am not sure how seriously to take these since I get a different test failure when I simply use the same Jenkins core baseline and the most recent released deps of the affected plugins:
In other words, we have a situation where PCT is not getting regularly run here, and at least some failures are not related to JEP-210. |
…se in test output.
If there is something you know ought to happen soon, but you are not exactly sure when, simply wait for it and let the test time out after 3m if it in fact never happens.
…Test.oneOrMoreArgsStepDocs.
@jglick PersistenceProblemsTests should be taken very seriously indeed. For me, if I use workflow-job 2.25 and everything else the same, these tests pass. And unfortunately they still fail with my AsynchronousExecution fix applied (so far), which suggests something deeper is amiss. |
Not for me, at least not quite. See #252 (comment).
Passes here after 15f2e7d. Just a bit of flakiness in the tests AFAICT, nothing to do with the upstream PRs except for slight changes in timing. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks reasonable to me, afaict -- would suggest cutting this into a portion that does not depend on the rewrite (so it's independently releasable) and then merging & releasing for workflow-cps.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The fixes here look reasonable to me.
(Note only reason I'm not approving is because it needs to be converted to something backported for merge there) |
At this point it may as well be merged since it is already picking up some parts of JEP-210. |
(and it is only a |
My own version of #251. Picks up jenkinsci/workflow-job-plugin#27, #253, #254, and jenkinsci/structs-plugin#41.