From @masak

<masak> rakudo​: my $a = 10; $a &&= 11; say $a
<p6eval> rakudo 54be6d​: OUTPUT«Null PMC access in invoke() [...]
* masak submits rakudobug
<masak> rakudo​: my $a = 10; $a = $a && 11; say $a
<p6eval> rakudo 54be6d​: OUTPUT«11␤»
<masak> so the error has to do with the &&= operator.
<masak> rakudo​: my $a = 0; $a ||= 11; say $a
<p6eval> rakudo 54be6d​: OUTPUT«Null PMC access in invoke() [...]

From @kyleha

This appears to be tested in S03-operators/assign.t (the tests are already
skipped with fudges).

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

From @bbkr

on Atlanta build​:

$ perl6 -e 'my $a = 10; $a &&= 11; say $a'
11
$ perl6 -e 'my $a = 0; $a ||= 11; say $a'
11

but fudged test sets still fails

From @bbkr

works on * release
tests in t/spec/S03-operators/assign.t unfudged

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