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
Fix for issue with p4 ticket parsing #4581
Conversation
Codecov Report
@@ Coverage Diff @@
## master #4581 +/- ##
==========================================
+ Coverage 88.44% 88.45% +<.01%
==========================================
Files 323 323
Lines 33658 33658
==========================================
+ Hits 29768 29771 +3
+ Misses 3890 3887 -3
Continue to review full report at Codecov.
|
I just duplicated the test. I'm trying to write a negative test too (for failed identification) but I have no idea how to run the testsuite. |
12f0b27
to
449202f
Compare
Rebased on top of current HEAD. |
@aisoard: Could you rebase on top of the current master again? During the release of v2.0 we broke the smokes test which is now fixed there. Thank you! |
Ok, I just rebased. Crossing fingers... |
In recent versions of Perforce CLI the output of `p4 login -p` changed. The ticket number is still on the last line of output (was 3rd line, is now 2nd line).
FIXME: P4Poller should probably fail on ticket parsing failure.
@p12tic @seankelly Am I missing something? |
I think you don't miss anything. @tardyp is the one who usually merges PRs, but there's several day latency most of the time. |
@aisoard thanks for the fix and tests! |
Proposed fix for P4 polling with ticket has incorrect parsing #4574.