sigb.us/dendrite
1
0
Fork 0
Code Issues Pull requests Actions Packages Projects Releases 1 Wiki Activity

Reduce cooldown to make sure sytest doesn't give up (#1257)

Browse source 
* Reduce cooldown to make sure sytest doesn't give up

* More sytests pass weeeeeee
This commit is contained in:
Kegsay 2020-08-11 10:44:59 +01:00 committed by GitHub
parent 52eeeb1627
commit befccd7d51
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 5 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
keyserver/internal/device_list_update.go
View file

@ -222,7 +222,8 @@ func (u *DeviceListUpdater) worker(ch chan gomatrixserverlib.ServerName) {
// last made a request to the server. If we get the server name during the cooloff // last made a request to the server. If we get the server name during the cooloff
// period, we'll ignore the poke. // period, we'll ignore the poke.
lastProcessed := make(map[gomatrixserverlib.ServerName]time.Time) lastProcessed := make(map[gomatrixserverlib.ServerName]time.Time)
cooloffPeriod := time.Minute // this can't be too long else sytest will give up trying to do a test
cooloffPeriod := 500 * time.Millisecond
shouldProcess := func(srv gomatrixserverlib.ServerName) bool { shouldProcess := func(srv gomatrixserverlib.ServerName) bool {
// we should process requests when now is after the last process time + cooloff // we should process requests when now is after the last process time + cooloff
return time.Now().After(lastProcessed[srv].Add(cooloffPeriod)) return time.Now().After(lastProcessed[srv].Add(cooloffPeriod))

3
sytest-whitelist
View file

@ -139,6 +139,9 @@ Get left notifs for other users in sync and /keys/changes when user leaves
Local device key changes get to remote servers Local device key changes get to remote servers
Local device key changes get to remote servers with correct prev_id Local device key changes get to remote servers with correct prev_id
Server correctly handles incoming m.device_list_update Server correctly handles incoming m.device_list_update
Device deletion propagates over federation
If remote user leaves room, changes device and rejoins we see update in sync
If remote user leaves room, changes device and rejoins we see update in /keys/changes
Can add account data Can add account data
Can add account data to room Can add account data to room
Can get account data without syncing Can get account data without syncing