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

Many spectest_regression tests fail to run #211

Closed
p6rt opened this issue Jul 31, 2008 · 5 comments
Closed

Many spectest_regression tests fail to run #211

p6rt opened this issue Jul 31, 2008 · 5 comments

Comments

@p6rt
Copy link

p6rt commented Jul 31, 2008

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

Searchable as RT57452$

@p6rt
Copy link
Author

p6rt commented Jul 31, 2008

From @masak

$ svn info | grep vi
Revision​: 29905

Many of the spectests look like this right now​:

t/spec/S02-builtin_data_types/anon_block...............src/string.c​:2091​:
failed assertion 's'
Backtrace - Obtained 14 stack frames (max trace depth is 32).
  Parrot_confess
  Parrot_confess
  string_to_cstring
  Parrot_open_p_s_sc
  dod_register_pmc
  interpinfo_s
  enable_event_checking
  Parrot_runops_fromc
  Parrot_runops_fromc_args
  Parrot_runcode
  imcc_initialize
  imcc_run
  start
  start

@p6rt
Copy link
Author

p6rt commented Jul 31, 2008

From @moritz

On Thu Jul 31 00​:31​:35 2008, masak wrote​:

$ svn info | grep vi
Revision​: 29905

Many of the spectests look like this right now​:

t/spec/S02-builtin_data_types/anon_block...............src/string.c​:2091​:
failed assertion 's'
Backtrace - Obtained 14 stack frames (max trace depth is 32).
Parrot_confess
Parrot_confess
...

same here.
I tried to bisect the problem, but it turns out to be really nasty​: svn
up'ping a revision $r, then rebuilding (after make realclean, of course)
didn't exhibit the problem. When I changed to another revision and then
got back to $r, and rebuilt, I saw the problem again.

So I suspect there are some leftovers in the tree that 'make realclean'
don't clean.

I suspect that the problem didn't exist on 2008-07-29, but I can't
really know of sure.

@p6rt
Copy link
Author

p6rt commented Jul 31, 2008

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

@p6rt
Copy link
Author

p6rt commented Aug 2, 2008

From @pmichaud

I'm not sure when/how this got fixed, but it appears to be working as of
r29933, so resolving ticket. (The bug is/was a parrot bug anyway.)

Pm

@p6rt
Copy link
Author

p6rt commented Aug 2, 2008

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

@p6rt p6rt closed this as completed Aug 2, 2008
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant