I am trying to get to the nightly build from the forum links that point to: nightly.z88dk.org/
Looks like the connection to the site is timing out. Is there a problem with the host server?
Owen
Nightly build URL not responding!?
-
- Member
- Posts: 14
- Joined: Mon Jan 22, 2024 8:48 am
Re: Nightly build URL not responding!?
I'm having the same problem now...
Re: Nightly build URL not responding!?
Hi
nightly build is down again
even the test suite is Not available
nightly build is down again
even the test suite is Not available
Code: Select all
zcc +test -m8080 -vn -a 8080/Issue_1531_opt_rule.c -o 8080/Issue_1531_opt_rule.opt.tmp1
diff -w 8080/Issue_1531_opt_rule.opt.tmp2 results/8080/Issue_1531_opt_rule.opt
make[1]: Leaving directory '/home/cb/z88dk/testsuite'
curl http://nightly.z88dk.org/zsdcc/zsdcc_r14648_src.tar.gz -o zsdcc_r14648_src.tar.gz
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- 0:00:03 --:--:-- 0
curl: (7) Failed to connect to nightly.z88dk.org port 80 after 3297 ms: No route to host
make: *** [Makefile:93: zsdcc_r14648_src.tar.gz] Error 7
Checking if submodule dependencies are met...
Module dependencies are present
make -C testsuite
make[1]: Entering directory '/home/cb/z88dk/testsuite'
make[1]: Nothing to be done for 'all'.
make[1]: Leaving directory '/home/cb/z88dk/testsuite'
curl http://nightly.z88dk.org/zsdcc/zsdcc_r14648_src.tar.gz -o zsdcc_r14648_src.tar.gz
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- 0:00:03 --:--:-- 0
curl: (7) Failed to connect to nightly.z88dk.org port 80 after 3177 ms: No route to host
make: *** [Makefile:93: zsdcc_r14648_src.tar.gz] Error 7
file 'test.c' not found
Code: Select all
ping nightly.z88dk.org
PING nightly.z88dk.org (45.153.221.151) 56(84) bytes of data.
64 bytes from 45.153.221.151 (45.153.221.151): icmp_seq=1 ttl=54 time=16.7 ms
64 bytes from 45.153.221.151 (45.153.221.151): icmp_seq=2 ttl=54 time=17.1 ms
64 bytes from 45.153.221.151 (45.153.221.151): icmp_seq=3 ttl=54 time=17.2 ms
64 bytes from 45.153.221.151 (45.153.221.151): icmp_seq=4 ttl=54 time=17.2 ms
64 bytes from 45.153.221.151 (45.153.221.151): icmp_seq=5 ttl=54 time=17.1 ms
64 bytes from 45.153.221.151 (45.153.221.151): icmp_seq=6 ttl=54 time=17.1 ms
64 bytes from 45.153.221.151 (45.153.221.151): icmp_seq=7 ttl=54 time=17.1 ms
64 bytes from 45.153.221.151 (45.153.221.151): icmp_seq=8 ttl=54 time=17.6 ms
64 bytes from 45.153.221.151 (45.153.221.151): icmp_seq=9 ttl=54 time=16.8 ms
64 bytes from 45.153.221.151 (45.153.221.151): icmp_seq=10 ttl=54 time=17.0 ms
64 bytes from 45.153.221.151 (45.153.221.151): icmp_seq=11 ttl=54 time=17.3 ms
64 bytes from 45.153.221.151 (45.153.221.151): icmp_seq=12 ttl=54 time=17.0 ms
64 bytes from 45.153.221.151 (45.153.221.151): icmp_seq=13 ttl=54 time=17.4 ms
64 bytes from 45.153.221.151 (45.153.221.151): icmp_seq=14 ttl=54 time=17.0 ms
64 bytes from 45.153.221.151 (45.153.221.151): icmp_seq=15 ttl=54 time=17.1 ms
64 bytes from 45.153.221.151 (45.153.221.151): icmp_seq=16 ttl=54 time=17.2 ms
64 bytes from 45.153.221.151 (45.153.221.151): icmp_seq=17 ttl=54 time=17.2 ms
64 bytes from 45.153.221.151 (45.153.221.151): icmp_seq=18 ttl=54 time=17.1 ms
64 bytes from 45.153.221.151 (45.153.221.151): icmp_seq=19 ttl=54 time=17.1 ms
64 bytes from 45.153.221.151 (45.153.221.151): icmp_seq=20 ttl=54 time=17.1 ms
64 bytes from 45.153.221.151 (45.153.221.151): icmp_seq=21 ttl=54 time=17.0 ms
64 bytes from 45.153.221.151 (45.153.221.151): icmp_seq=22 ttl=54 time=16.9 ms
64 bytes from 45.153.221.151 (45.153.221.151): icmp_seq=23 ttl=54 time=16.8 ms
64 bytes from 45.153.221.151 (45.153.221.151): icmp_seq=24 ttl=54 time=17.2 ms
64 bytes from 45.153.221.151 (45.153.221.151): icmp_seq=25 ttl=54 time=17.3 ms
64 bytes from 45.153.221.151 (45.153.221.151): icmp_seq=26 ttl=54 time=17.1 ms
64 bytes from 45.153.221.151 (45.153.221.151): icmp_seq=27 ttl=54 time=16.7 ms
^C
--- nightly.z88dk.org ping statistics ---
27 packets transmitted, 27 received, 0% packet loss, time 26042ms
rtt min/avg/max/mdev = 16.718/17.086/17.576/0.194 ms
Re: Nightly build URL not responding!?
Sorry, for some reason the proxy VM keeps dropping off the network and leaves nothing in the logs to indicate why.
My suspicion is that something on my network doesn't like VLANs (I've got a couple of other problems) but nothing concrete yet,
Anyway, if it happens again let me know and I'll give it a kick.
My suspicion is that something on my network doesn't like VLANs (I've got a couple of other problems) but nothing concrete yet,
Anyway, if it happens again let me know and I'll give it a kick.