diff --git a/server/.taprc b/server/.taprc
index d39c3b66a..caaf45c5d 100644
--- a/server/.taprc
+++ b/server/.taprc
@@ -1,8 +1,7 @@
 files: "src/test-utils/single-process-tap.ts"
 test-env: [NODE_ENV=test, TCHIS_CONF_LOCATION=test.conf.json5]
 # On a local machine, these tests run in under 2-3 minutes.
-# On github actions, these tests take an inordinate amount of time.
-# I do not know why, and it suddenly started happening one day.
+# On github actions, these tests can take an inordinate amount of time.
 # The timeout is set to 16 minutes, which is ridiculous.
 # Doesn't matter for real machines.
 timeout: 960
diff --git a/server/src/lib/score-import/framework/calculated-data/calculated-data.test.ts b/server/src/lib/score-import/framework/calculated-data/calculated-data.test.ts
index ffd792f4b..dfe825478 100644
--- a/server/src/lib/score-import/framework/calculated-data/calculated-data.test.ts
+++ b/server/src/lib/score-import/framework/calculated-data/calculated-data.test.ts
@@ -385,43 +385,6 @@ t.test("#CalculateDataForGamePT", (t) => {
 
 		t.end();
 	});
-	// t.test("jubeat:Single", async (t) => {
-	// 	const res = await CalculateDataForGamePT(
-	// 		"jubeat",
-	// 		"Single",
-	// 		Testing511SPA,
-	// 		TestingIIDXSPDryScore, // fake! this is an iidx score. but we're testing
-	// 		null,
-	//
-	// 		logger
-	// 	);
-
-	// 	prAssert(t ,
-	// 		res,
-	// 		{
-	// 			jubility: "?number",
-	// 		},
-	// 		"Response should contain nulled keys for jubeat:Single"
-	// 	);
-
-	// 	t.end();
-	// });
-
-	// t.test("popn:9B", async (t) => {
-	// 	const res = await CalculateDataForGamePT(
-	// 		"popn",
-	// 		"9B",
-	// 		Testing511SPA,
-	// 		TestingIIDXSPDryScore, // fake! this is an iidx score. but we're testing
-	// 		null,
-	//
-	// 		logger
-	// 	);
-
-	// 	prAssert(t ,res, {}, "Response should contain nulled keys for popn:9B");
-
-	// 	t.end();
-	// });
 
 	t.end();
 });