Ryan Lovelett wrote on 08/14/2016 05:10:34 PM:
>
> However, the `dispatch_io` test is still failing. I've added the
> test-suite.log once more.
>
Hi Ryan,
The test that is failing creates a temporary directory, sets it to be
read-only, and then attempts to write into the directory. I
That seems about right. The tests run in a chroot, where the script is
root, to ensure that I control dependencies and such.
Not sure what I I can do about this test. 🤔
Thanks for the help Dave!
On Mon, Aug 15, 2016, at 10:57 AM, David P Grove wrote:
> Ryan Lovelett wrote on 08/14/2016
> 05:10:
Hi, swift-dev et al (but especially Ted). I’ve recently noticed that our JIRA
workflow has been a bit confusing. We currently have five “statuses":
1. Opened: This bug has been filed.
2. In Progress: Someone is actively working on this bug. (Not everyone has been
bothering to set this, but it se
Do we anticipate Verify being used in practice much?
Would it be better to simplify the workflow and just have a single
"Resolved/Closed/Done" state? If the originator does test the bug and find it
isn't fixed, they can reopen.
My guess is not that many people are going to actively look at the
It hasn’t been used so much so far, but on the bugs where it has I like being
able to tell the difference. I don’t think we’d poke people about verification
like we do with Radar, though, so we will (and have) end up with a lot of bugs
left in Resolved/Verify.
Jordan
> On Aug 15, 2016, at 10:
