Megatest

Check-in [69d1d314cd]
Login
Overview
Comment:Re-enabling the updater as it works fine on SLES11!
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | v1.65-try3
Files: files | file ages | folders
SHA1: 69d1d314cd31b774f4336fa2c8906e4387696013
User & Date: mrwellan on 2019-12-04 14:26:45
Other Links: branch diff | manifest | tags
Context
2019-12-06
04:16
moved the old compilation unit files to the attic, removed some debug stuff of Brandons, TODO: put that stuff into a module and enable use of it. check-in: 7e32aa8d9e user: matt tags: v1.65-try3
2019-12-04
14:26
Re-enabling the updater as it works fine on SLES11! check-in: 69d1d314cd user: mrwellan tags: v1.65-try3
2019-12-03
22:30
Removed junk character from dashboard.scm check-in: 7ed5a5de19 user: matt tags: v1.65-try3
Changes

Modified dashboard.scm from [31ec6121f3] to [a80924c869].

3164
3165
3166
3167
3168
3169
3170
3171
3172
3173
3174
3175
3176
3177
3178
				  (set! update-is-running (dboard:commondat-updating commondat))
				  (if (not update-is-running)
				      (dboard:commondat-updating-set! commondat #t))
				  (mutex-unlock! (dboard:commondat-update-mutex commondat))
				  (if (not update-is-running) ;; we know that the update was not running and we now have a lock on doing an update
				      (begin
					;; this function is causing memory segfault:
				  	;; (dboard:common-run-curr-updaters commondat) ;; (dashboard:run-update commondat)
					(mutex-lock! (dboard:commondat-update-mutex commondat))
				  	(dboard:commondat-updating-set! commondat #f)
					(mutex-unlock! (dboard:commondat-update-mutex commondat))
					)
				     )
				1))
			      "Action callback")))))







|







3164
3165
3166
3167
3168
3169
3170
3171
3172
3173
3174
3175
3176
3177
3178
				  (set! update-is-running (dboard:commondat-updating commondat))
				  (if (not update-is-running)
				      (dboard:commondat-updating-set! commondat #t))
				  (mutex-unlock! (dboard:commondat-update-mutex commondat))
				  (if (not update-is-running) ;; we know that the update was not running and we now have a lock on doing an update
				      (begin
					;; this function is causing memory segfault:
				  	(dboard:common-run-curr-updaters commondat) ;; (dashboard:run-update commondat)
					(mutex-lock! (dboard:commondat-update-mutex commondat))
				  	(dboard:commondat-updating-set! commondat #f)
					(mutex-unlock! (dboard:commondat-update-mutex commondat))
					)
				     )
				1))
			      "Action callback")))))