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
on "/".IO.mkdir #4899
Comments
From @labster01:56 labster m: "/".IO.mkdir # well that's a surprise Also segfaults on OS X. JVM behavior looks OK. The upside is that Perl 6 is so terse, you can segfault in only 10 |
From @smlsNo longer segfaults with current r-m: ➜ "/".IO.mkdir; Ticket should be closable once a test has been added to Roast. |
The RT System itself - Status changed from 'new' to 'open' |
From @zoffixznet
Is it really appropriate to attempt to create such directories? I'm hesitant to have roast touch things outside of its directory. |
From @zoffixznetTests added: Raku/roast@423ee643ea |
@zoffixznet - Status changed from 'open' to 'resolved' |
From @ninerWithout having checked this, it looks to me like the bug was not about trying to create the root directory, but a failure to handle a permission problem trying to create a directory. If that's true, then the test should easily be able to re-create the circumstances. Just create a temporary directory and remove your own write permissions. Then try to create a subdirectory which should fail of course. Then you can remove the temporary directory again. |
From @geekosaurOn Mon, Jul 4, 2016 at 6:44 PM, Zoffix Znet via RT <
It's a directory that must always exist and therefore always fail in a -- |
From zoffix@zoffix.comAnd when a bug creeps in and destroy's someone's system? We already It's fine to check failure modes on an existing directory we create Cheers, Quoting Brandon Allbery <allbery.b@gmail.com>:
|
From zoffix@zoffix.comOr we could have some extra tests category for dangerous tests. I know make stresstest does extra tests. Would this test fit into those? Quoting zoffix@zoffix.com:
|
From @geekosaurOn Tue, Jul 5, 2016 at 12:06 AM, <zoffix@zoffix.com> wrote:
The only way that would misbehave would indicate a system already corrupted -- |
Migrated from rt.perl.org#126976 (status was 'resolved')
Searchable as RT126976$
The text was updated successfully, but these errors were encountered: