Groups
Conversations
All groups and messages
Send feedback to Google
Help
Training
Sign in
Groups
Devel::NYTProf Dev
Conversations
About
[timbunce/devel-nytprof] c0c2b2: Update test expectations for strawberry perl porta...
0 views
Skip to first unread message
Tim Bunce
unread,
Jun 4, 2018, 8:37:29 AM
6/4/18
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to develnyt...@googlegroups.com
Branch: refs/heads/master
Home:
https://github.com/timbunce/devel-nytprof
Commit: c0c2b20a990e095051934eb8e3ab7737ec6ad3fd
https://github.com/timbunce/devel-nytprof/commit/c0c2b20a990e095051934eb8e3ab7737ec6ad3fd
Author: Shawn Laffan <
shawn...@gmail.com
>
Date: 2018-06-04 (Mon, 04 Jun 2018)
Changed paths:
M t/40-savesrc.t
M t/lib/NYTProfTest.pm
Log Message:
-----------
Update test expectations for strawberry perl portable
Strawberry perl portable versions return different eval IDs,
presumably due to some eval calls prior to the profile start.
For example, '(eval 5)[-:1]' is returned instead of '(eval 1)[-:1]'.
Update the tests to identify when this happens, and to then correct for it.
Commit: 9047c75fa946bf08e625d68594090826b1eb600a
https://github.com/timbunce/devel-nytprof/commit/9047c75fa946bf08e625d68594090826b1eb600a
Author: Tim Bunce <
Tim....@pobox.com
>
Date: 2018-06-04 (Mon, 04 Jun 2018)
Changed paths:
M t/40-savesrc.t
M t/lib/NYTProfTest.pm
Log Message:
-----------
Merge pull request #123 from shawnlaffan/portable_strawberry_tests
Update test expectations for strawberry perl portable.
Closes #76 and #94, I hope.
Compare:
https://github.com/timbunce/devel-nytprof/compare/92bf605cd780...9047c75fa946
**NOTE:** This service been marked for deprecation:
https://developer.github.com/changes/2018-04-25-github-services-deprecation/
Functionality will be removed from GitHub.com on January 31st, 2019.
Reply all
Reply to author
Forward
0 new messages