Skip to content
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

Test module reports incorrect line number #3769

Closed
p6rt opened this issue Apr 1, 2015 · 12 comments
Closed

Test module reports incorrect line number #3769

p6rt opened this issue Apr 1, 2015 · 12 comments

Comments

@p6rt
Copy link

p6rt commented Apr 1, 2015

Migrated from rt.perl.org#124227 (status was 'resolved')

Searchable as RT124227$

@p6rt
Copy link
Author

p6rt commented Mar 24, 2015

From @tbrowder

The Test module almost always reports line 1 for every failure
regardless of which test. This behavior is seen in the latest
release​:

  $ perl6 -v
  This is perl6 version 2015.03-48-g9746e88 built on MoarVM version 2015.03

as well as the previous release.

The behavior can be witnessed by cloning
"https://github.com/tbrowder/Geo-Ellipsoid-perl6.git" locally and
running​:

  $ make test

Two of many failures from one test input​:

<quote>

# Failed test at t/02-defaults.t line 1
not ok 8 -

# Failed test at t/02-defaults.t line 1
not ok 9 -

</quote>

-Tom

<tbrowder>

@p6rt
Copy link
Author

p6rt commented Apr 1, 2015

From @drforr

The Test module appears to be reporting failure at the wrong line
number.

Test file - Note the test that will fail is at line 8, the bottom of the
file​:
--cut here--
use v6;

use Test;

plan 2;

ok 1;
ok 0;
--cut here--

Test output - Note 'line 1' should be 'line 8'.
--cut here--
1..2
ok 1 -
not ok 2 -

# Failed test at test.t line 1
# Looks like you failed 1 tests of 2
--cut here--

@p6rt
Copy link
Author

p6rt commented Apr 2, 2015

From @perlpilot

Seems to be fixed by 3a8ecbc92066ce27d4a705339a7ed59e44c4e2b6

-Scott

On Wed Apr 01 13​:22​:51 2015, drforr@​pobox.com wrote​:

The Test module appears to be reporting failure at the wrong line
number.

Test file - Note the test that will fail is at line 8, the bottom of the
file​:
--cut here--
use v6;

use Test;

plan 2;

ok 1;
ok 0;
--cut here--

Test output - Note 'line 1' should be 'line 8'.
--cut here--
1..2
ok 1 -
not ok 2 -

# Failed test at test.t line 1
# Looks like you failed 1 tests of 2
--cut here--

--
perlpilot

@p6rt
Copy link
Author

p6rt commented Apr 2, 2015

The RT System itself - Status changed from 'new' to 'open'

@p6rt
Copy link
Author

p6rt commented Apr 2, 2015

@perlpilot - Status changed from 'open' to 'resolved'

@p6rt
Copy link
Author

p6rt commented Apr 2, 2015

From @coke

Re-opening, marking test needed.

--
Will "Coke" Coleda

1 similar comment
@p6rt
Copy link
Author

p6rt commented Apr 2, 2015

From @coke

Re-opening, marking test needed.

--
Will "Coke" Coleda

@p6rt
Copy link
Author

p6rt commented Apr 2, 2015

@coke - Status changed from 'resolved' to 'open'

@p6rt
Copy link
Author

p6rt commented Apr 8, 2015

From @usev6

I added some tests to S24-testing/line-numbers.t with commit Raku/roast@4317b37e35.

This new test file is not included in t/spectest.data in Rakudo, yet, so I'm leaving this ticket open.

1 similar comment
@p6rt
Copy link
Author

p6rt commented Apr 8, 2015

From @usev6

I added some tests to S24-testing/line-numbers.t with commit Raku/roast@4317b37e35.

This new test file is not included in t/spectest.data in Rakudo, yet, so I'm leaving this ticket open.

@p6rt
Copy link
Author

p6rt commented Apr 8, 2015

From @coke

On Wed Apr 08 08​:28​:46 2015, bartolin@​gmx.de wrote​:

I added some tests to S24-testing/line-numbers.t with commit
Raku/roast@4317b37e35.

This new test file is not included in t/spectest.data in Rakudo, yet,
so I'm leaving this ticket open.

That test passes, added to t/spectest.data

Closing ticket.

--
Will "Coke" Coleda

@p6rt p6rt closed this as completed Apr 8, 2015
@p6rt
Copy link
Author

p6rt commented Apr 8, 2015

@coke - Status changed from 'open' to 'resolved'

@p6rt p6rt added the testneeded label Jan 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant