Followed the tutorial to run a first experiment which failed https://doc.fed4fire.eu/firstexperiment.html
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Oct 21 2021
Followed the tutorial https://doc.fed4fire.eu/tools.html
$ time tox -e py3 -- --basetemp=/mnt/pytest -s --shard-size $((100 * 1024)) --object-max-size $((4 * 1024)) -k test_build_speed number of objects = 45973694, total size = 105903024192 baseline 165.74853587150574, write_duration 495.07564210891724, build_duration 24.210500478744507, total_duration 519.2861425876617
@ardumont I believe all your comments were addressed. It is lucky that you did not review the actual logic: while running benchmarks I ran into a bug that lead to a significant refactor (using fread/fwrite instead of mmap and addresses). Not to the point where you'll have to re-read everything from scratch though 馃槄
Build is green
using mmap turned out to be more involved than expected, use
read/write instead
Oct 20 2021
I have created a new Jenkins pipeline job manually to experiment on setting up that new CI build.
Build has FAILED
Build has FAILED
Build has FAILED
Closing here the tests of the workers.
Thanks!
Build is green
See https://jenkins.softwareheritage.org/job/DDOC/job/build-on-diff/9/ for more details.
Build is green
document the build_objstorage() test helper function
Build is green
Build is green
remove useless statement
remove mistakenly commited mypy.ini file
Build has FAILED
lgtm
This is the impact of configuration the add batch insert size. Tested values were 500, 1000 and 2000.
A full repair of a cassandra node was in progress due to a datalost (disk erased by someone else's experiment after the disk reservation expiration)
Build is green
Build has FAILED
rebase
remove a (comment) garbage line
Build has FAILED
Build has FAILED
rebase
slight simplification as suggested by vlorentz
Build is green
Build has FAILED
Build has FAILED
respawn jenkins
respawn jenkins
Rebase
Rebase
It has been implemented and deployed to production, closing this.
It has been implemented and deployed to production, closing this.
Build has FAILED
rebase
It's been done for a while. We can see it appearing in the main archive page under cgit.
Remains 6 origins still ongoing...
After further investigation, I can't find any directory that is in a completely bad order; they are either ordered like git does (by adding a / at the end of dir entries) or by assuming a null byte at the end of dir entries.
I've opened T3674 to discuss how to properly reference origins that are not the output of listers.
Build has FAILED
split the diff in 2
New webapp version deployed [1], we can see the mercurial origins referenced as a discontinued service there.