Commit graph

9 commits

Author SHA1 Message Date
35a944d896
Revert "See if it helps to allow unlimited locked memory"
Some checks failed
/ container (push) Has been cancelled
We can not increase the ulimit from inside the job, instead we need to
tell forgejo (via /opt/forgejo-runner/data/config.yml) to include
e.g. "--ulimit memlock=-1" in container options if necessary.

This did not appear to help things however.

This reverts commit 2be4c8ea13.
2025-02-28 08:34:28 +01:00
2be4c8ea13
See if it helps to allow unlimited locked memory
Some checks failed
/ container (push) Failing after 1m53s
2025-02-27 23:48:51 +01:00
75f6318e45
Go back to varnish 7.6.1 and the latest SLASH/
Some checks failed
/ container (push) Failing after 2h58m48s
This reverts commit 98c759557e.
2025-02-27 20:49:42 +01:00
3ba28004c8
Revert "Investigate state of /tmp"
This reverts commit 5963b0b2d9.
2025-02-27 20:49:07 +01:00
5963b0b2d9
Investigate state of /tmp
All checks were successful
/ container (push) Successful in 11m38s
2025-02-27 15:34:58 +01:00
98c759557e
Revert changes
All checks were successful
/ container (push) Successful in 11m50s
Build still gets stuck, lets see if it works again now.
2025-02-27 15:10:11 +01:00
74c01574d2
Update to latest varnish
Some checks failed
/ container (push) Has been cancelled
Currently the build hangs i SLASH/ tests.
Build output where it hangs:
```
make  check-TESTS check-local
1338
make[3]: Entering directory '/tmp/slash/src'
1339
make[4]: Entering directory '/tmp/slash/src'
1340
PASS: fellow_cache_test_ndebug
```

The binary that is hanging: ./fellow_cache_test
2025-02-27 13:14:25 +01:00
2682839756
Update SLASH/
Some checks failed
/ container (push) Has been cancelled
Should fix problem reported in
https://gitlab.com/uplex/varnish/slash/-/issues/92
2025-02-27 11:29:36 +01:00
af7f7d11e6
Initial commit
All checks were successful
/ container (push) Successful in 13m15s
2024-10-04 12:48:34 +02:00