-
Notifications
You must be signed in to change notification settings - Fork 24
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
Running multiple qiimes concurrently before refreshing the cache causes fireworks #186
Comments
We should probably write the config to a temp location and move it after it is fully written, then we won't have to mess with locking or other things like that. |
Wow this is an older issue!
Same JSONDecodeError as it tramples over itself. Is this something you'd be interested in helping with @danteese? |
For sure, old issue!
As you can see I'm not able to reproduce the exit 1 with the JSONDecodeError. My first thought would be the version of qiime2-dev but I'm not sure ... |
Running the same command in a linux machine I wasn't able to replicate
the problem. All jobs finished without any problem.
…On (Sep-17-19|15:53), Dante Bazaldua wrote:
For sure, old issue!
And it's quite interesting because this is your execution in my computer:
```
(qiime2-dev) > $ for i in `seq 1 20`; do qiime dev refresh-cache & done
[2] 79152
[3] 79153
[4] 79154
[5] 79155
[6] 79156
[7] 79157
[8] 79158
[9] 79159
[10] 79160
[11] 79161
[12] 79162
[13] 79163
[14] 79164
[15] 79165
[16] 79166
[17] 79167
[18] 79168
[19] 79169
[20] 79170
[21] 79171
***@***.***_64-apple-darwin13 ~ [17:45:17]
(qiime2-dev) > $ QIIME is caching your current deployment for improved performance. This may take a few moments and should only happen once per deployment.
QIIME is caching your current deployment for improved performance. This may take a few moments and should only happen once per deployment.
QIIME is caching your current deployment for improved performance. This may take a few moments and should only happen once per deployment.
QIIME is caching your current deployment for improved performance. This may take a few moments and should only happen once per deployment.
QIIME is caching your current deployment for improved performance. This may take a few moments and should only happen once per deployment.
QIIME is caching your current deployment for improved performance. This may take a few moments and should only happen once per deployment.
QIIME is caching your current deployment for improved performance. This may take a few moments and should only happen once per deployment.
QIIME is caching your current deployment for improved performance. This may take a few moments and should only happen once per deployment.
QIIME is caching your current deployment for improved performance. This may take a few moments and should only happen once per deployment.
QIIME is caching your current deployment for improved performance. This may take a few moments and should only happen once per deployment.
QIIME is caching your current deployment for improved performance. This may take a few moments and should only happen once per deployment.
QIIME is caching your current deployment for improved performance. This may take a few moments and should only happen once per deployment.
QIIME is caching your current deployment for improved performance. This may take a few moments and should only happen once per deployment.
QIIME is caching your current deployment for improved performance. This may take a few moments and should only happen once per deployment.
QIIME is caching your current deployment for improved performance. This may take a few moments and should only happen once per deployment.
QIIME is caching your current deployment for improved performance. This may take a few moments and should only happen once per deployment.
QIIME is caching your current deployment for improved performance. This may take a few moments and should only happen once per deployment.
QIIME is caching your current deployment for improved performance. This may take a few moments and should only happen once per deployment.
QIIME is caching your current deployment for improved performance. This may take a few moments and should only happen once per deployment.
QIIME is caching your current deployment for improved performance. This may take a few moments and should only happen once per deployment.
[17] 79167 done qiime dev refresh-cache
[4] 79154 done qiime dev refresh-cache
(qiime2-dev) > $
[19] 79169 done qiime dev refresh-cache
(qiime2-dev) > $
[15] 79165 done qiime dev refresh-cache
(qiime2-dev) > $
[12] 79162 done qiime dev refresh-cache
(qiime2-dev) > $
[11] 79161 done qiime dev refresh-cache
(qiime2-dev) > $
[10] 79160 done qiime dev refresh-cache
(qiime2-dev) > $
[9] 79159 done qiime dev refresh-cache
(qiime2-dev) > $
[7] 79157 done qiime dev refresh-cache
(qiime2-dev) > $
[6] 79156 done qiime dev refresh-cache
(qiime2-dev) > $
[5] 79155 done qiime dev refresh-cache
(qiime2-dev) > $
[3] 79153 done qiime dev refresh-cache
(qiime2-dev) > $
[21] + 79171 done qiime dev refresh-cache
(qiime2-dev) > $
[20] + 79170 done qiime dev refresh-cache
(qiime2-dev) > $
[18] + 79168 done qiime dev refresh-cache
(qiime2-dev) > $
[16] + 79166 done qiime dev refresh-cache
(qiime2-dev) > $
[14] + 79164 done qiime dev refresh-cache
(qiime2-dev) > $
[13] + 79163 done qiime dev refresh-cache
(qiime2-dev) > $
[8] + 79158 done qiime dev refresh-cache
(qiime2-dev) > $
[2] + 79152 done qiime dev refresh-cache
```
As you can see I'm not able to reproduce the exit 1 with the JSONDecodeError. My first thought would be the version of qiime2-dev but I'm not sure ...
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
#186 (comment)
|
You both must have nicer computers than me. What about 100 iterations? Really we just need it to read as the file is being written. |
Bug Description
I tried to run 10 qiimes concurrently before I had refreshed the cache.
My log follows. Manually refreshing the cache before starting fixed the problem.
Screenshots
Click to expand!
The text was updated successfully, but these errors were encountered: