roocs / clisops / 40337587264
87%

DEFAULT BRANCH: master
Ran
Jobs 4
Files 32
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 86.921%. Remained the same
40337587264

push

github

web-flow 
Bump filelock from 3.25.2 to 4.2.1 in /CI (#526)

Bumps [filelock](https://github.com/tox-dev/py-filelock) from 3.25.2 to
4.2.1.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/tox-dev/py-filelock/releases">filelock's
releases</a>.</em></p>
<blockquote>
<h2>4.2.1</h2>
<ul>
<li>On a singleton wrapper, <code>close&gt;</code> and
<code>close&gt;</code> end only the holds that tasks acquired
through that wrapper. A reader that arrives during <code>close()</code>
gets the closed error instead of joining the ending hold.
After synchronous code closes or force-releases the shared lock, the
wrappers refuse to admit readers into the ended
hold, and <code>close()</code> on such a wrapper returns.
Closing one wrapper no longer ends a task's nested hold taken through
another wrapper on the same path. <a
href="https://redirect.github.com/tox-dev/py-filelock/issues/832">#832</a></li>
<li><code>ReadWriteLock</code> locks again after a
<code>release()</code> that an exception from a signal handler
interrupted.
The async read-write wrappers stop admitting readers into such a level.
The async read-write locks forget a hold whose
backend release failed after the backend let go, and they free the
memory of each acquire that times out or is canceled.
<code>AsyncFileLock</code> returns from <code>release()</code> after a
few hundred acquires gave up behind a waiting one. An exception from a
signal handler delivered while an <code>AsyncFileLock</code> call joins
its queue no longer blocks every later call on that lock. <a
href="https://redirect.github.com/tox-dev/py-filelock/issues/833">#833</a></li>
<li>Fix <code>ReadWriteLock</code> acting on <code>-journal</code>,
<code>-wal</code> or <code>-shm</code> files another process puts beside
its
database: a write could land in another file, a reader could get in
beside a writer, and an acquire could fail. SQLite
now opens the database by name only in a directory no other account can
w... (continued)

3210 of 3693 relevant lines covered (86.92%)

3.48 hits per line

Jobs
ID Job ID Ran Files Coverage
1 run-Python3.12-conda - 40337587264.1 32
86.92
GitHub Action Run
2 run-Python3.13-conda - 40337587264.2 32
86.92
GitHub Action Run
3 run-Python3.11-conda - 40337587264.3 32
86.92
GitHub Action Run
4 run-Python3.14-conda - 40337587264.4 32
86.92
GitHub Action Run
Source Files on build 40337587264