Closed p5pRT closed 11 years ago
Another hand TAP to test.pl conversion
On Sat Sep 08 15:34:37 2012\, colink@perldreamer.com wrote:
Another hand TAP to test.pl conversion
This is the output I got after applying the patch:
######## $ ./perl t/op/append.t ok 1 - compile time concatenation ok 2 - concat to self ok 3 - concat using $_ ok 4 ok 5 ok 4 - null bytes get copied ok 7 ok 5 ok 9 ok 6 ok 11 ok 7 ok 13 1..7 #########
It appears we still have some manually constructed test output. Can you fix?
Also\, I like the fact that you have added labels for 3 of the tests. Could you do so for the remaining 10?
Thank you very much. Jim Keenan
P.S.: You don't have to prepend the subject with 'TODO task: '. AFAICT\, that doesn't set the "Todo" type\, which someone has to set manually.
The RT System itself - Status changed from 'new' to 'open'
All patched up.
Also\, in subsequent patches I'll try to add as many labels/names as possible.
On Sun Sep 09 14:42:03 2012\, colink@perldreamer.com wrote:
All patched up.
Also\, in subsequent patches I'll try to add as many labels/names as possible.
Colin\, your most recent patch pertains to t/uni/case.pl -- and has already been applied :-) (be250cb1944\, July 18 2012)
Do you have a second patch for t/op/append.t?
Thank you very much. Jim Keenan
There has to be an easier way to manage all these patches. What I've done is to clone a git branch off of blead\, make a series of commits\, and then use format-patch to get patches that I can send. When the patches clear\, then I delete and recreate the branch. Suggestions or clue-bats welcome.
On Tue\, Sep 11\, 2012 at 06:41:26PM -0700\, Colin Kuskie via RT wrote:
There has to be an easier way to manage all these patches. What I've done is to clone a git branch off of blead\, make a series of commits\, and then use format-patch to get patches that I can send. When the patches clear\, then I delete and recreate the branch. Suggestions or clue-bats welcome.
You can just keep the commits directly on blead\, and use 'git pull --rebase' when updating. It will be smart enough to notice when commits are applied\, and not duplicate them. If you want to keep things on a separate branch\, just use 'git rebase blead' whenever you want to update it\, it will have the same effect.
-doy
On 09/12/2012 03:41 AM\, Colin Kuskie via RT wrote:
There has to be an easier way to manage all these patches. What I've done is to clone a git branch off of blead\, make a series of commits\, and then use format-patch to get patches that I can send. When the patches clear\, then I delete and recreate the branch. Suggestions or clue-bats welcome.
Thanks\, applied as 18b94ad2978e118214353bdd240628c63557c0c8 unless I have to rebase/retest again after tests finish.
--Steffen
On Wed\, Sep 12\, 2012 at 12:54 AM\, Steffen Mueller \smueller@​cpan\.org wrote:
On 09/12/2012 03:41 AM\, Colin Kuskie via RT wrote:
There has to be an easier way to manage all these patches. What I've done is to clone a git branch off of blead\, make a series of commits\, and then use format-patch to get patches that I can send. When the patches clear\, then I delete and recreate the branch. Suggestions or clue-bats welcome.
Thanks\, applied as 18b94ad2978e118214353bdd240628c63557c0c8 unless I have to rebase/retest again after tests finish.
--Steffen
What's up with the eval{} lines?
- print eval '$t4 =~ /$ub/' ? "ok 9\n" : "not ok 9\t# $t4\n"; + eval { like( $t4\, qr/$ub/\, '... \0a\0a\0b' ); };
Good question. From the digging I did in git\, they were part of the original set of tests that were added to this file. I'm assuming that those tests died in the regex engine\, and he didn't want the test to die either.
On Tue Sep 11 22:56:02 2012\, smueller@cpan.org wrote:
On 09/12/2012 03:41 AM\, Colin Kuskie via RT wrote:
There has to be an easier way to manage all these patches. What I've done is to clone a git branch off of blead\, make a series of commits\, and then use format-patch to get patches that I can send. When the patches clear\, then I delete and recreate the branch. Suggestions or clue-bats welcome.
Thanks\, applied as 18b94ad2978e118214353bdd240628c63557c0c8 unless I have to rebase/retest again after tests finish.
--Steffen
Steffen\,
If you feel this ticket is closable\, please feel free to do so.
Thank you very much. Jim Keenan
I restored some logic related to those evals (need to be string evals) based on some archaeology. This change applied as a5d38fd9a576445bb00ac5ac3b195e659b56c470daff0d3c7d.
The relevant commit goes back a bit and refers to EBCDIC compatibility:
commit 933bc096593f55b9633fb193815ddd81d5b5ec1b
Author: Jarkko Hietaniemi \jhi@​iki\.fi
Date: Tue Nov 27 01:22:22 2001 +0000
\141 is malformed "unexpected continuation byte" in UTF-EBCDIC.
Delay the match until runtime.
I restored some logic related to those evals (need to be string evals) based on some archaeology. This change applied as a5d38fd9a576445bb00ac5ac3b195e659b56c470daff0d3c7d.
The relevant commit goes back a bit and refers to EBCDIC compatibility:
commit 933bc096593f55b9633fb193815ddd81d5b5ec1b
Author: Jarkko Hietaniemi \jhi@​iki\.fi
Date: Tue Nov 27 01:22:22 2001 +0000
\141 is malformed "unexpected continuation byte" in UTF-EBCDIC.
Delay the match until runtime.
@tsee - Status changed from 'open' to 'resolved'
On Thu Oct 04 23:29:32 2012\, smueller@cpan.org wrote:
I restored some logic related to those evals (need to be string evals) based on some archaeology. This change applied as a5d38fd9a576445bb00ac5ac3b195e659b56c470daff0d3c7d.
I went looking for that commit with 'git show' and couldn't find it.
However\, I found it here: 76445bb00ac5ac3b195e659b56c470daff0d3c7d
Am I misunderstanding something about commit numbers?
Thank you very much. Jim Keenan
* James E Keenan via RT \perlbug\-followup@​perl\.org [2012-10-05 16:50]:
Am I misunderstanding something about commit numbers?
No. That object simply doesn’t exist in perl5.git.
On 10/05/2012 02:00 PM\, James E Keenan via RT wrote:
On Thu Oct 04 23:29:32 2012\, smueller@cpan.org wrote:
I restored some logic related to those evals (need to be string evals) based on some archaeology. This change applied as a5d38fd9a576445bb00ac5ac3b195e659b56c470daff0d3c7d.
I went looking for that commit with 'git show' and couldn't find it.
However\, I found it here: 76445bb00ac5ac3b195e659b56c470daff0d3c7d
Am I misunderstanding something about commit numbers?
No\, you simply overestimated me. When I do open source stuff\, I'm usually on a bad connection on a train. So I prepare the RT replies and all for when I have a usable link. In the mornings\, shortly after 7am in Europe\, it's really rather rare for others to be committing. Usually\, I still check whether I had to rebase-before-push before hitting "Update ticket". Sometimes\, that doesn't work so well before my first coffee. :(
In other words: Sorry about that!
--Steffen
Migrated from rt.perl.org#114796 (status was 'resolved')
Searchable as RT114796$