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

Non-zero wait status: 11 in testt #2567

Open
robertlemmen opened this Issue Dec 24, 2018 · 10 comments

Comments

Projects
None yet
4 participants
@robertlemmen
Copy link

robertlemmen commented Dec 24, 2018

builds of 2018.12 on ppc64el failed during tests:

https://buildd.debian.org/status/fetch.php?pkg=rakudo&arch=ppc64el&ver=2018.12-1&stamp=1545495855&raw=0

the problem seems to happen only rarely, but running t/02-rakudo/08-inline-native-arith.t in a loop eventually led to this slightly information-free reproduction:

Test Summary Report
-------------------
t/08-performance/99-misc.t (Wstat: 11 Tests: 0 Failed: 0)
  Non-zero wait status: 11
  Parse errors: No plan found in TAP output
Files=1, Tests=0,  1 wallclock secs ( 0.02 usr  0.01 sys +  0.56 cusr  0.02 csys =  0.61 CPU)
Result: FAIL

Please let me know what I can do to help debug this

@AlexDaniel AlexDaniel added the BLOCKER label Dec 24, 2018

@robertlemmen

This comment has been minimized.

Copy link
Author

robertlemmen commented Jan 8, 2019

this may actually be a duplicate of #2564 ...

@AlexDaniel

This comment has been minimized.

Copy link
Member

AlexDaniel commented Jan 18, 2019

@robertlemmen #2564 was resolved, can you check it again?

@niner

This comment has been minimized.

Copy link
Contributor

niner commented Jan 18, 2019

The fix for #2564 was specific to CStruct, so I'd be surprised if there's a change in 99-misc.t

@AlexDaniel

This comment has been minimized.

Copy link
Member

AlexDaniel commented Jan 21, 2019

@dogbert17 have you tried reproducing this? It's not a big endian issue, so should probably also happen on amd64.

@AlexDaniel AlexDaniel added the SEGV label Jan 21, 2019

@JJ

This comment has been minimized.

Copy link
Contributor

JJ commented Jan 21, 2019

Not a problem running Rakudo version 2018.12-207-g0d9e9f34c built on MoarVM version 2018.12-13-g473324ee3

@AlexDaniel

This comment has been minimized.

Copy link
Member

AlexDaniel commented Jan 21, 2019

Yeah, I've been running it in a loop and got nothing. @robertlemmen can you perhaps check it again? Maybe something else fixed it…

@JJ

This comment has been minimized.

Copy link
Contributor

JJ commented Jan 21, 2019

@robertlemmen

This comment has been minimized.

Copy link
Author

robertlemmen commented Jan 21, 2019

I just re-ran the original looped test on ppc64el, but with newer moar (g34fac5f4e), nqp (gbd7bf00b5) and rakudo (g5b231e099), which relatively quickly resulted in a:

===SORRY!===
Cannot invoke this object (REPR: Null; VMNull)
@AlexDaniel

This comment has been minimized.

Copy link
Member

AlexDaniel commented Feb 20, 2019

Was there any change in behavior during the last month? What's the current status?

@AlexDaniel

This comment has been minimized.

Copy link
Member

AlexDaniel commented Feb 23, 2019

I think this comment applies here too: #2576 (comment)
Can't tell if this issue is completely new or if we just didn't notice it before for some reason, but for now we will have to let it be.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.